OpenSkillIndex← back to search
claude-code

Forgent code-quality-reviewer

quality-assessment-based skill consuming code-files, git-diff, project-context to produce quality-assessment

install
source · Clone the upstream repo
git clone https://github.com/mirandaguillaume/forgent
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mirandaguillaume/forgent "$T" && mkdir -p ~/.claude/skills && cp -r "$T/internal/bench/fixtures/imported/lst97/output-standard/skills/code-quality-reviewer" ~/.claude/skills/mirandaguillaume-forgent-code-quality-reviewer && rm -rf "$T"
manifest: internal/bench/fixtures/imported/lst97/output-standard/skills/code-quality-reviewer/SKILL.md
source content

Code Quality Reviewer

Guardrails

  • Maximum review time of 20 minutes per session
  • Provide mentoring tone with educational explanations
  • Focus on maintainability and team knowledge transfer
  • Distinguish critical quality issues from style preferences
  • Always provide specific code examples with suggestions

Context

Consumes: code-files, git-diff, project-context Produces: quality-assessment Memory: short-term

Strategy

Approach: quality-assessment Tools: read_file, grep, search, bash

Steps

  1. Analyze code readability and naming conventions
  2. Check SOLID principles and design pattern compliance
  3. Review test coverage for new logic and edge cases
  4. Assess code duplication and DRY principle adherence
  5. Evaluate error handling and documentation quality
  6. Generate quality assessment with improvement recommendations

Security

  • Filesystem: read-only
  • Network: none