Agent skill
session-cleanup
Verify debug/dev artifacts are removed before commit. Use at session end to apply 'good boy scout' rule - leave code cleaner than you found it.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/session-cleanup-wildcard-caro-5d2ca462
SKILL.md
Session Cleanup Skill
What This Skill Does
This skill verifies that debug and development artifacts are cleaned up before committing code. It embodies the "good boy scout" principle: leave the code cleaner than you found it.
Key Responsibilities:
- Find debug print statements (eprintln!, dbg!, println! for debug)
- Find commented-out debug code
- Find leftover test files or temporary code
- Report any cleanup needed before commit
When to Use This Skill
Use this skill:
- At the end of a debug/investigation session
- Before creating a commit
- After fixing a bug to ensure debug code is removed
- When you've been adding/removing diagnostic code
Automatic Reminder: Consider adding to your session-end routine.
Manual Triggers:
/session-cleanup- "Check for debug artifacts"
- "Clean up session"
Artifacts to Find
Rust Debug Artifacts
// These should be removed before commit:
eprintln!("DEBUG: ..."); // Debug prints
println!("[DEBUG] ..."); // Debug prints
dbg!(variable); // Debug macro
#[allow(dead_code)] // Only if for debug code
// TODO: REMOVE // Temporary markers
Temporary Test Code
// Look for these patterns:
#[test]
fn temp_test() { ... } // Temporary tests
#[ignore] // Tests that should be removed or fixed
fn test_disabled() { ... }
Debug Logging Levels
// These are fine (production logging):
tracing::debug!(...); // OK - controlled by log level
tracing::info!(...); // OK - informational
// These may be debug artifacts:
tracing::warn!("DEBUG: ..."); // Suspicious - debug in warn?
Cleanup Checklist
When running this skill:
-
Scan for eprintln!/println! debug
bashgrep -rn "eprintln!" src/ | grep -i debug grep -rn 'println!.*DEBUG' src/ -
Scan for dbg! macros
bashgrep -rn 'dbg!' src/ -
Scan for TODO markers
bashgrep -rn 'TODO.*REMOVE\|TEMPORARY\|DEBUG' src/ -
Check for test artifacts
bashgrep -rn 'temp_test\|test_debug' src/ tests/ -
Review git diff for debug additions
bashgit diff --cached | grep -E '^\+.*eprintln|^\+.*dbg!'
Example Session Flow
[During Debug Session]
- Add eprintln! statements to trace execution
- Add temporary tests to verify fixes
- Use dbg! for quick value inspection
[At Session End]
- Invoke /session-cleanup
- Remove all debug artifacts found
- Verify changes still work
- Commit clean code
Integration
This skill pairs well with:
/commit- Run cleanup before committing/validate-constitution- Validate standards after cleanup- Git pre-commit hooks - Automatic detection
Remember
- Debug code is useful during development
- Debug code should NOT be committed
- The "good boy scout" rule: leave code cleaner than you found it
- A few minutes of cleanup saves reviewers time
This skill ensures debug artifacts from investigation sessions don't pollute the codebase.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?