BrowserOS dev6-review-fix

Apply fixes for review comments from dev5-review and commit. Sub-skill of the /dev workflow.

install
source · Clone the upstream repo
git clone https://github.com/browseros-ai/BrowserOS
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/browseros-ai/BrowserOS "$T" && mkdir -p ~/.claude/skills && cp -r "$T/packages/browseros-agent/.claude/skills/dev6-review-fix" ~/.claude/skills/browseros-ai-browseros-dev6-review-fix && rm -rf "$T"
manifest: packages/browseros-agent/.claude/skills/dev6-review-fix/SKILL.md
source content

Dev Workflow — Step 6: Fix Review Comments

You are applying fixes for the code review comments.

Input

  1. Read
    .llm/$ARGUMENTS/tmp_review.md
    for the review comments
  2. Read
    .llm/$ARGUMENTS/prd.md
    for 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):

  1. Read the referenced file and line
  2. Apply the fix
  3. 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
.