Gsd code review fix
Handy AI skills
npx -y skills add bitrails-dev/skills --skill gsd-code-review-fixAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
SKILL.md
2.1 KB, 432 tokens by cl100k_base, as published. Nobody here has run it
Arguments:
- Phase number (required) — which phase's REVIEW.md to fix (e.g., "2" or "02")
--all(optional) — include Info findings in fix scope (default: Critical + Warning only)--auto(optional) — enable fix + re-review iteration loop, capped at 3 iterations
Output: {padded_phase}-REVIEW-FIX.md in phase directory + inline summary of fixes applied </objective>
<execution_context> @$HOME/.claude/get-shit-done/workflows/code-review-fix.md </execution_context>
<context> Phase: $ARGUMENTS (first positional argument is phase number)Optional flags parsed from $ARGUMENTS:
--all— Include Info findings in fix scope. Default behavior fixes Critical + Warning only.--auto— Enable fix + re-review iteration loop. After applying fixes, re-run code-review at same depth. If new issues found, iterate. Cap at 3 iterations total. Without this flag, single fix pass only.
Context files (CLAUDE.md, REVIEW.md, phase state) are resolved inside the workflow via gsd-sdk query init.phase-op and delegated to agent via config blocks.
</context>
Execute the code-review-fix workflow from @$HOME/.claude/get-shit-done/workflows/code-review-fix.md end-to-end.
The workflow (not this command) enforces these gates:
- Phase validation (before config gate)
- Config gate check (workflow.code_review)
- REVIEW.md existence check (error if missing)
- REVIEW.md status check (skip if clean/skipped)
- Agent spawning (gsd-code-fixer)
- Iteration loop (if --auto, capped at 3 iterations)
- Result presentation (inline summary + next steps) </process>