quick-review

What This Skill Does

The quick-review skill acts as an intelligent, automated pair programmer within your development environment. It is designed to scrutinize your git diffs—whether staged or unstaged—to identify high-impact issues before you commit your code. Instead of focusing on cosmetic linting or trivial style preferences, this skill targets substantial problems that affect system stability, security, and maintainability. By automating the identification of logic errors, security vulnerabilities, performance bottlenecks, and dead code, quick-review helps maintain high-quality standards across your codebase.

Installation

To integrate this skill into your OpenClaw workflow, execute the following command in your terminal: clawhub install openclaw/skills/skills/jagger-zxz/zxz-test

Use Cases

1. Pre-Commit Gatekeeping: Use this before running git commit to ensure your latest changes don't introduce critical bugs or security flaws.
2. Pull Request Preparation: Run this skill to self-review your code before pushing to a remote repository, significantly reducing the cognitive load on your human peer reviewers.
3. Quick Debugging: When debugging a specific feature branch, run this to get a fresh pair of eyes on the logic changes you just implemented.

Example Prompts

1. "Review my current changes and let me know if there are any security vulnerabilities or logic errors I missed."
2. "I'm about to commit these changes, can you check for any potential performance issues or hardcoded credentials?"
3. "Please scan my staged changes and summarize any bugs or code quality issues before I push this update."

Tips & Limitations

• Focus on Action: The skill is programmed to avoid subjective feedback. It ignores trivial formatting issues to provide you with actionable, high-value advice.
• Scope: The effectiveness of the skill is limited to the current diff. If a bug exists outside the changed lines, it will not be detected. Always maintain a comprehensive test suite in addition to this review.
• Contextual Accuracy: Because the skill references exact line numbers and variable names, ensure your git diff output is readable. If the diff is excessively large, consider reviewing components modularly for better analysis accuracy.