Prepare code for commit by checking for bugs, ensuring consistency, removing debug code, and running checks until green. Use when finishing a feature, before committing, or when asked to "make it green" or "prep for commit".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Prepare code for commit by checking for bugs, ensuring consistency, removing debug code, and running checks until green. Use when finishing a feature, before committing, or when asked to "make it green" or "prep for commit".
Finalize
Prepare code for commit by systematically checking for issues and running checks until everything passes.
When to Use
Invoke /finalize when:
Finishing a feature or bug fix
User asks to "make it green", "prep for commit", or "production ready"
Before handing code back to user for commit
After a significant implementation session
Note: This skill prepares code for commit but does NOT create the commit itself.
Before Starting
Identify scope - What files were changed in this session?
git diff --name-only HEAD
git diff --cached --name-only
Understand context - What was implemented? This informs what edge cases to check.
Phase 1: Bug Check
Review changed files for common bugs and edge cases.
Checklist
Null/Undefined Handling:
Optional chaining used where data might be undefined
Fallback values provided for potentially missing data
Array methods handle empty arrays gracefully
Edge Cases:
Empty states handled (empty arrays, null objects)
Error states handled (network failures, invalid input)
Loading states don't cause crashes
Boundary conditions checked (0, negative, max values)
Logic Errors:
Conditionals have correct operators (=== vs ==, && vs ||)
Async/await used correctly (no missing await)
Event handlers don't cause infinite loops
State updates don't cause stale closures
Type Safety:
No implicit any types
Type assertions (as) are justified
Validation at system boundaries (user input, external APIs)
Phase 1b: Critical Path Review
Configure this section for your project's high-risk areas.
console.log() - Remove unless it's intentional production logging
console.debug() - Remove all
console.warn() - Keep only if warning is useful in production
console.error() - Keep if it's error reporting
debugger statements - Remove all
Commented-out code - Remove unless there's a clear reason
// TODO from this session - Keep and warn user (see below)
Test data / hardcoded values - Replace with real implementation
Production Logging Guidelines:
console.error() - OK for actual errors that should be visible
Structured logging (logger.info/warn/error) - OK if using logging framework
Any other console.* - Remove
TODO Handling
Search for TODOs in changed files:
git diff --name-only HEAD | xargs grep -n "TODO\|FIXME\|XXX\|HACK" 2>/dev/null
Action:
If TODO was created in this session: Warn user - present the list and ask if they should be addressed or left
If TODO existed before: Leave as-is
Never silently remove TODOs
Other Production Checks
No hardcoded localhost URLs (except in env examples)
No hardcoded API keys or secrets
No test-only code in production paths
Error messages are user-friendly, not developer-speak
No placeholder text ("Lorem ipsum", "TODO", "CHANGEME")
Phase 4: Run Tests
Run the test suite to catch regressions:
# Use your project's test command
npm test# or: yarn test, pnpm test, pytest, dotnet test, etc.
If tests fail:
Identify which tests failed
Determine if failure is due to:
Bug in new code → Fix it
Test needs updating for new behavior → Update test
Unrelated flaky test → Note and continue
Re-run tests after fixes
Test Coverage:
New functionality should have tests
If no tests exist for changed code, warn user
Phase 5: Make It Green
Run the full check suite and fix issues iteratively.
# Use your project's check/lint command
npm run check
# or: npm run lint && npm run typecheck && npm run build
Iteration Loop
1. Run check command
2. If passes → Done!
3. If fails:
a. Identify the failing step (format/lint/typecheck/build)
b. Fix the issues
c. Go to step 1
Common Fixes
Format issues:
Usually auto-fixed by formatter
If persisting, check for syntax errors
Lint issues:
Read the error message carefully
Common: unused imports, missing dependencies
Fix: Remove unused code, add missing deps
Type issues:
Type mismatches: Check expected vs actual types
Missing properties: Add required fields or make optional
Import errors: Check package exports
Build issues:
Usually caused by type errors
Check for circular dependencies
Verify all imports resolve
Max Iterations
If after 5 iterations issues persist:
Stop and report remaining issues
Ask user for guidance on unresolved problems
Final Report
After all phases complete, present summary:
## Finalize Summary### Changes Reviewed- {N} files checked
### Issues Found & Fixed- Removed {N} console.log statements
- Fixed {N} lint errors
- Fixed {N} type errors
### Warnings- {N} TODOs remain in code:
-`path/to/file.ts:123` - TODO: description
### Status
✅ All checks passing - Ready for commit
### Files Changed
{list of files modified during finalize}
Checklist
Before completing:
Bug check completed on all changed files
Critical path review if changes touch high-risk areas
Consistency check completed
Debug code removed (console.log, debugger)
TODOs reviewed and user warned if any remain
Tests pass
Check command passes (green)
Summary report presented to user
No commit created (user will commit)
Anti-Patterns
// ❌ Leaving debug codeconsole.log('data:', data) // Remove!debugger// Remove!// ✓ Production-appropriate logging
logger.error('Failed to process request', { id, error })
// ❌ Silently removing TODOs// (just delete TODO comments without telling user)// ✓ Warn about TODOs// "Found 2 TODOs in changed files. Should I address these or leave them?"
// ❌ Giving up after first failure// "Check failed, here are the errors"// ✓ Iterating until green// Fix errors → re-run → repeat until passing
// ❌ Creating a commit
git commit -m "..."// Don't do this!// ✓ Just prep the code// "All checks passing. Ready for you to commit."
