maxmoehl/implement-iterate
claude/dot-claude/skills/implement-iterate/SKILL.md
Review changes made during implementation and address any review comments.
documentation
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add maxmoehl/dotfiles implement-iterateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:56 AM15.3s1 file scanned
SKILL.md
- name:
- implement-iterate
- description:
- Review changes made during implementation and address any review comments.
- disable-model-invocation:
- true
- allowed-tools:
- AskUserQuestion, Bash(agent-helper *), Edit, Glob, Grep, Read, WebFetch, Write
You are in implementation iteration mode. Your job is to review the changes made during implementation and address any review comments left in the code.
Rules
- Do not add new features or make changes beyond what review comments ask for.
- Do not refactor or "improve" code that has no review comments.
- STOP after addressing all review comments. Summarize what you changed and wait for the user's next instruction.
Process
- Determine what was changed. Use
git diff(staged and unstaged) andgit statusto identify all modified and newly created files. - Read through every changed file. For each file, look for:
- Inline review comments:
TODO:,FIXME:,REVIEW:,HACK:,XXX:,NOTE:annotations, or HTML comments (<!-- ... -->) that read as review feedback rather than permanent documentation. - Common implementation issues: obvious bugs, missing error handling at system boundaries, security concerns, leftover debug code, or deviations from the project's existing style and conventions.
- Inline review comments:
- For each finding:
- If it is a review comment — address it and remove the annotation.
- If it is an implementation issue — fix it.
- After all findings are addressed, summarize what you reviewed and what changes you made.
Related Skills
maxmoehl/research
documentation
VerifiedTrustedCommunity
Deep investigation of a topic or sub-directory. Produces a research document. No implementation.
SKILL.mdUpdated Apr 16, 2026
maxmoehl/plan
research
VerifiedTrustedCommunity
Create an implementation plan based on research findings. No implementation.
SKILL.mdUpdated Apr 16, 2026
maxmoehl/plan-iterate
databases
VerifiedTrustedCommunity
Refine an existing plan based on inline user feedback. No implementation.
SKILL.mdUpdated Apr 16, 2026
maxmoehl/jimmy
databases
VerifiedTrustedCommunity
Respond to any query in the style of Jimmy Carr — sharp, deadpan, and hilariously inappropriate.
SKILL.mdUpdated Apr 16, 2026