gsd-review-fix

Apply atomic fixes with DCO sign-off and verify via tests and re-review.

6|3|Updated Mar 31, 2026

Search Tags:#verification #code-review #quality-gates #atomic-commit #gsd #dco

Ready to run

npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-review-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-review-fix
Source: https://github.com/alo-exp/silver-bullet/tree/main/skills/gsd-review-fix
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-review-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often reveal findings that must be addressed across the codebase. This Skill provides a disciplined, repeatable workflow to fix findings with atomic commits and validate changes via the review process.

Core Features & Use Cases

Prioritized remediation: fix CRITICAL findings first, then MAJOR, then MINOR.
Atomic commits with DCO: each fix is committed with a descriptive message and signed off.
Verification & re-review: run tests and lints, then re-run code review to confirm all findings are resolved.
Wide applicability: suitable for teams needing consistent, auditable review-cycle closures.

Quick Start

Review all findings, apply atomic commits for each fix, and re-run code review to verify resolution.

Frequently Asked Questions about gsd-review-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix code review findings with atomic commits?▼

Fix code review findings by applying atomic fixes across multiple files, prioritizing CRITICAL and MAJOR issues first. Each fix requires a clear commit message and DCO sign-off to ensure auditable, repeatable remediation cycles.

What is the best way to verify code review findings are resolved?▼

Verify resolved code review findings by running tests and lints, then re-run the code review step to confirm all issues are closed. This validation ensures your atomic fixes successfully address the original findings across the codebase.

Does fixing code review findings require DCO sign-off for each commit?▼

Yes, fixing code review findings requires DCO sign-off for each atomic commit. This ensures a disciplined, auditable workflow where every applied fix is tracked with a descriptive commit message and verified during the review process.

How do I prioritize remediation when resolving code review findings?▼

Prioritize remediation of code review findings by fixing CRITICAL issues first, then MAJOR, then MINOR. This structured approach ensures the most severe findings are resolved and validated with tests before addressing lower-priority items.

Can I use this code review fix workflow for formal software reviews?▼

Yes, you can use this workflow for software projects undergoing formal reviews. It provides a disciplined, repeatable process to apply atomic fixes across multiple files, making it suitable for teams needing consistent review-cycle closures.

Why should I use atomic commits when resolving code review findings?▼

Atomic commits isolate individual code review fixes, ensuring clear commit messages and DCO sign-off for each change. This approach maintains a clean project history and simplifies verification by re-running tests and the code review step.