address review

Engineering Community

Skill notes

Step 1: Identify the PR and Feature Folder

Run git branch --show-current to get the current branch. Derive the feature folder: Strip the feat/ prefix from the branch name. Extract the first path segment (everything before the second /) — this is the feature slug. Feature folder = spec/features/[slug]/

Step 2: Pull Unresolved Comments

Use gh api repos/{owner}/{repo}/pulls/{number}/comments to get all review comments. Filter for unresolved/pending comments (not yet resolved by the author). Group comments by category: Code Comments General code review feedback — bugs, style, logic issues, suggestions.

Step 3: Address Code Comments

For each unresolved code comment: Read the referenced file and line range. Understand the reviewer's concern. Fix the code to address the concern. If the fix requires test changes, update tests and ensure they pass.

Step 4: Handle Spec Proposals

Read SPEC-PROPOSAL.md from the feature folder (if it exists). For Approved Proposals Read the proposal entry (e.g. SP-001). Apply the proposed change to the actual spec file (e.g. update REQUIREMENTS.md, ADR.md, or DESIGN.md in the feature folder). Remove the approved entry from SPEC-PROPOSAL.md.

Step 5: Run Tests

Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Identify the PR and Feature Folder

Run `git branch --show-current` to get the current branch. Derive the feature folder: Strip the `feat/` prefix from the branch name. Extract the first path segment (everything before the second `/`) — this is the feature slug. Feature folder = `spec/features/[slug]/`

02
Step 2: Pull Unresolved Comments

Use `gh api repos/{owner}/{repo}/pulls/{number}/comments` to get all review comments. Filter for unresolved/pending comments (not yet resolved by the author). Group comments by category: Code Comments General code review feedback — bugs, style, logic issues, suggestions.

03
Step 3: Address Code Comments

For each unresolved code comment: Read the referenced file and line range. Understand the reviewer's concern. Fix the code to address the concern. If the fix requires test changes, update tests and ensure they pass.

04
Step 4: Handle Spec Proposals

Read `SPEC-PROPOSAL.md` from the feature folder (if it exists). For Approved Proposals Read the proposal entry (e.g. SP-001). Apply the proposed change to the actual spec file (e.g. update `REQUIREMENTS.md`, `ADR.md`, or `DESIGN.md` in the feature folder). Remove the approved entry from `SPEC-PROPOSAL.md`.

05
Step 5: Run Tests

Run the full test suite (or at minimum, tests related to the changes) to ensure everything passes after the fixes.

06
Step 6: Commit and Push

Stage all modified files. Commit with message: `fix(NNNN-slug): address review comments for {ISSUE-ID}` Push to the current branch.

07
Step 7: Report

Present a summary: Number of comments addressed Code changes made Spec proposals approved/rejected and files updated Whether SPEC-PROPOSAL.md was cleaned up

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.