staged-code-review

What problem does it solve?

This Skill provides a final quality gate before committing code by analyzing staged git changes to detect debug leftovers, hardcoded secrets, missing error handling, and framework-specific issues, preventing regressions and security risks from entering the repository.

Core Features & Use Cases

• Staged diff analysis: Reads staged changes, counts changed files, and summarizes modified file types to detect the applicable tech stack.
• Tech-stack-aware checks: Applies language and framework specific rules for React/TypeScript, Vue, Go, Python, Java/Kotlin, Rust, and more to catch common anti-patterns.
• Security and quality gates: Flags debug statements, hardcoded credentials, missing error handling, and boundary-condition issues and classifies problems as blocking or advisory.
• Commit message generation: Creates conventional commit messages and supports parameterized linking of Story, Task, or Bug IDs for traceability.
• Use Case: Run this as the last local check before git commit to reduce PR churn, avoid shipping secrets, and standardize commit messages.

Quick Start

Ask the skill to review your staged changes and generate a conventional commit message, for example: please review my staged changes and propose a commit message linking --story=STORY-123 if applicable.