team-review

Perform inline code reviews on feature branches for compliance and bugs.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/AirMile/claude-config --skill team-review-airmile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-review
Source: https://github.com/AirMile/claude-config/tree/main/skills/team-review
Command: npx skills add https://github.com/AirMile/claude-config --skill team-review-airmile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates inline code reviews on feature branches to surface compliance issues, bugs, and historical insights, reducing manual review time and increasing confidence before PRs.

Core Features & Use Cases

  • CLAUDE.md compliance checks: Validate project-specific rules and conventions during review.
  • Bug and quality analysis: Detect logical errors, potential regressions, and code-quality issues from diffs.
  • History-aware review: Leverage git blame and history context to ground findings and justify changes.
  • PR integration ready: Optionally post review comments back to pull requests to streamline collaboration.

Quick Start

To start a review, trigger the /team-review skill on your feature branch and follow the prompts to select Quick or Full review.

Frequently Asked Questions about team-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate inline code reviews on a feature branch?

Automating inline code reviews on a feature branch involves analyzing git diffs to detect bugs and compliance issues. This skill performs diff-based bug detection, validates project rules, and calculates confidence scores to reduce manual review time.

What is CLAUDE.md compliance checking in code review?

CLAUDE.md compliance checking is the process of validating project-specific rules and conventions during a code review. It automatically enforces defined standards by analyzing feature branch diffs against your configured CLAUDE.md guidelines.

How can I use git history to improve pull request comments?

Using git history like blame data improves pull request comments by grounding review findings in historical context. This approach analyzes past changes to justify current diff detections and provide accurate inline PR commentary.

Does Context7 best-practice research enrich code quality analysis?

Context7 best-practice research enriches code quality analysis by integrating external standards into the review process. It leverages optional context lookups to supplement diff-based bug detection and strengthen the justification for inline findings.

Can I post structured inline review findings directly to pull requests?

Posting structured inline review findings directly to pull requests is supported through optional PR integration. This automates posting compliance issues, bug detections, and confidence scores back to the pull request comments.

What is the best way to standardize code reviews across a team?

The best way to standardize code reviews across a team is to automate diff analysis with rule-based compliance checks. Applying consistent CLAUDE.md validations and confidence scoring eliminates manual variability in feature branch evaluations.