athal7/respond-to-review
skills/respond-to-review/SKILL.md
Address review feedback on your own merge request — resolve threads fixed by a commit, reply to threads you are not addressing
$ install --global
skillsauthnpx skillsauth add athal7/dotfiles respond-to-reviewInstall 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: May 20, 2026, 2:08 AM60.2s1 file scanned
SKILL.md
- name:
- respond-to-review
- description:
- Address review feedback on your own merge request — resolve threads fixed by a commit, reply to threads you are not addressing
- license:
- MIT
- compatibility:
- opencode
-
Fetch all open review threads. Note thread ID, file, line, comment body, author, resolved status.
-
Plan a stance per thread as a list —
fixordecline-with-reason— before any code changes. Do not propose follow-up issues or deferred work as a stance; if the work is genuinely tracked elsewhere, that is adecline-with-reasonwhose reason cites the existing tracking. -
Verify the plan: every thread has a stance, fix-stance has a test-first approach, decline-stance has a substantive reason. Apply findings.
-
Work through every thread:
- Fix: follow strict red/green/refactor (your standing TDD instructions apply). Present a per-file summary (reviewer comment beside addressing diff) and wait for acknowledgement, then commit with a message referencing the feedback. Resolve the thread — no reply needed.
- Decline: do NOT resolve. Post an inline reply on the thread (not a top-level comment) using the thread's top comment ID, explaining why the code isn't changing.
-
Push. The source control host ties thread resolution to the commit, so push before resolving or replying.
-
Verify coverage. Re-fetch threads; every one must be either resolved or have a reply from you. Never hand back with threads that have neither.
-
Re-request review from every reviewer who previously reviewed.
Rules:
- Resolve silently when a commit fixes — no "fixed" reply.
- Reply without resolving when declining — never silently resolve a disagreement.
- Never resolve a thread you didn't fix.
Related Skills
athal7/zoom
development
VerifiedTrustedCommunity
Zoom meeting captions — file locations and format
6SKILL.mdUpdated May 24, 2026
athal7/dictation
tools
VerifiedTrustedCommunity
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
6SKILL.mdUpdated May 24, 2026
athal7/knowledge-base
testing
VerifiedTrustedCommunity
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
6SKILL.mdUpdated May 21, 2026
athal7/communication
testing
VerifiedTrustedCommunity
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions
6SKILL.mdUpdated May 21, 2026