finishing-work
Use when completing work on a task or feature. Prompts for code review before finishing. ALWAYS invoke this skill before saying work is done.
When & Why to Use This Skill
The 'Finishing Work' Claude skill acts as a quality gatekeeper for software development tasks. It ensures code integrity by mandating a code review prompt before any task is marked as complete, integrating seamlessly with automated review pipelines like CodeRabbit to detect bugs and improve maintainability.
Use Cases
- Feature Completion: Automatically prompting for a code review after finishing a new feature to ensure the code meets project standards before merging.
- Automated Quality Assurance: Triggering the CodeRabbit pipeline (request, triage, and fix) to identify and resolve potential issues without manual intervention.
- Workflow Standardization: Enforcing a consistent 'Definition of Done' across development tasks by requiring a review confirmation before the agent stops work.
- Bug Fix Validation: Ensuring that patches and hotfixes are reviewed and triaged to prevent regressions before the task is finalized.
| name | finishing-work |
|---|---|
| description | Use when completing work on a task or feature. Prompts for code review before finishing. ALWAYS invoke this skill before saying work is done. |
Finishing Work
CRITICAL: Always Ask About Code Review
Before finishing ANY work, you MUST ask the user:
"Would you like me to request a code review before finishing? (Yes/No)"
Use the AskUserQuestion tool with options:
- Yes - Invoke
coderabbit-requestskill, then triage and fix any issues - No - Skip review and proceed to finish
Do NOT skip this prompt. Even for small changes, the user decides.
If User Says Yes: Code Review Workflow
Invoke coderabbit-request to start the review pipeline:
coderabbit-request
↓ (outputs JSON)
coderabbit-triage
↓ (outputs task plan)
coderabbit-fix (parallel or sequential)