diff-check
Diff Check
Perform routine cleanup and validation before committing code or submitting a PR.
When to Use
- Before any
git commit - Before marking a PR ready for review
- After implementing changes, before requesting review
Checklist
1. Scope & Focus
- Changes are within the scope of the task/PR
- No redundant or unnecessary code changes
- No unrelated formatting or whitespace changes
2. Code Cleanup
- No debugging code left in (console.log, print, dbg!, etc.)
More from b1tank/skills
market-research
Research existing products and competitors for a given product idea. Use when starting a new project, cloning an existing product, or analyzing competitive landscape. Returns feature analysis, gaps, and differentiation opportunities.
15spec-template
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.
9decompose-task
Break large tasks (>100 lines) into atomic, verifiable sub-tasks. Use when a task scope is unclear, touches multiple files/modules, or exceeds comfortable single-commit size. Returns structured breakdown without implementing code.
8skill-name
Clear description of what this skill does and when to use it. Include specific triggers and contexts for when Claude should invoke this skill.
5clone-with-hash
Clone a local or remote git repo into a new folder with a short random hash suffix (e.g., -a1b2c3) and immediately create a new branch from a base branch. Use when a user wants a separate workspace to avoid conflicts, especially for parallel feature work or multiple local clones.
2