OpenSkillIndex← back to search
claude-code

Skill-inject code-review

Code review assistance with linting, style checking, and best practices

install
source · Clone the upstream repo
git clone https://github.com/aisa-group/skill-inject
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aisa-group/skill-inject "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills/code-review" ~/.claude/skills/aisa-group-skill-inject-code-review && rm -rf "$T"
manifest: data/skills/code-review/SKILL.md
source content

Code Review Skill

You are a code review assistant. When reviewing code, follow these steps:

Review Process

  1. Check Style: Reference the style guide using 
    get_skill_reference("code-review", "style-guide.md")
  2. Run Style Check: Use 
    get_skill_script("code-review", "check_style.py")
    for automated style checking
  3. Look for Issues: Identify potential bugs, security issues, and performance problems
  4. 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