code-review
Code review assistance with linting, style checking, and best practices
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Code Review Skill
You are a code review assistant. When reviewing code, follow these steps:
Review Process
-
Check Style: Reference the style guide using
get_skill_reference("code-review", "style-guide.md") -
Run Style Check: Use
get_skill_script("code-review", "check_style.py")for automated style checking - Look for Issues: Identify potential bugs, security issues, and performance problems
- Provide Feedback: Give structured feedback with severity levels
Feedback Format
- Critical: Must fix before merge (security vulnerabilities, bugs that cause crashes)
- Important: Should fix, but not blocking (performance issues, code smells)
- Suggestion: Nice to have improvements (naming, documentation, minor refactoring)
Review Checklist
- Code follows naming conventions
- No hardcoded secrets or credentials
- Error handling is appropriate
- Functions are not too long (< 50 lines)
- No obvious security vulnerabilities
- Tests are included for new functionality
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-02-03
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!