Dev Workflow — Step 6: Fix Review Comments
SkillAI & modelsApply fixes for review comments from dev5-review and commit. Sub-skill of the /dev workflow.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Dev Workflow — Step 6: Fix Review Comments skill
What this skill tells your AI
The instructions your AI receives, as published by browseros-ai/browseros-agent in .claude/skills/dev6-review-fix/SKILL.md and read by ahel’s review.
You are applying fixes for the code review comments.
Input
- Read
.llm/$ARGUMENTS/tmp_review.mdfor the review comments - Read
.llm/$ARGUMENTS/prd.mdfor context on what the feature should do
Step 1: Triage comments
Read all review comments. Group them:
- Critical — Must fix. Bugs, security issues, correctness problems.
- Suggestions — Should fix. Code quality, readability improvements.
- Nits — Fix if quick. Minor style preferences.
Step 2: Apply fixes
For each comment (starting with critical, then suggestions, then nits):
- Read the referenced file and line
- Apply the fix
- Verify the fix doesn't break anything (run tests if applicable)
Step 3: Verify
Run the test suite to make sure fixes didn't introduce regressions.
Step 4: Commit
Stage and commit the review fixes:
git add -A && git commit -m "fix: address review comments for $ARGUMENTS"
Step 5: Hand off
Tell the user review fixes are applied and committed, then immediately invoke /dev7-pr $ARGUMENTS.
Signals
- GitHub stars
- 51
- Forks
- 40
- Last commit
- Jun 2026
Advanced
- Catalog kind
- skill
- Gateway key
dev6-review-fix- Source
- github.com/browseros-ai/browseros-agent