Agent skill

code-review

Review code changes using CodeRabbit CLI - supports uncommitted files (task mode) or all PR files vs main branch (pr mode). Catches bugs, security issues, and code quality problems before committing or when reviewing pull requests. Use when: (1) Reviewing uncommitted changes before committing (task mode), (2) Reviewing all changed files in a PR against main branch (pr mode), (3) Working on subtasks and want to check progress, (4) Need feedback on work-in-progress code, (5) Preparing PR for merge, (6) When CodeRabbit review is needed, (7) For bug detection and security scanning, or (8) For automated code quality assessment. Triggers: review code, check code quality, review changes, code review, review PR, check for bugs, security scan, review uncommitted, finalize code, pre-commit review.

Stars 2
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/LukasStrickler/ai-dev-atelier/tree/main/content/skills/code-review

Metadata

Additional technical details for this skill

author
ai-dev-atelier
version
1.0

SKILL.md

Code Review

Two Modes

Task Mode (Uncommitted Files)

Reviews only uncommitted files in the working directory. Use for work-in-progress code before committing.

Command: bash skills/code-review/scripts/review-run.sh task

How it works:

  • Scans all uncommitted files (git status shows as modified/untracked)
  • Sends files to CodeRabbit for review
  • Saves results to .ada/data/reviews/task-review-{timestamp}.md

PR Mode (All Files vs Main)

Reviews all changed files in the current branch compared to the main branch. Use for complete PR review.

Command: bash skills/code-review/scripts/review-run.sh pr

How it works:

  • Compares current branch against main branch (or configured base branch)
  • Reviews all changed files in the diff
  • Saves results to .ada/data/reviews/pr-review-{timestamp}.md

Tools

  • ada::review:task - Review uncommitted changes
  • ada::review:pr - Review all PR files vs main branch
  • ada::review:read - Read latest review results
  • ada::review:cleanup - Clean up old review files

Workflow

Task Mode Workflow

  1. Make code changes: Edit files without committing
  2. Run review: Execute bash skills/code-review/scripts/review-run.sh task
    • CodeRabbit analyzes uncommitted files
    • Review is saved to .ada/data/reviews/
  3. Read results: Run bash skills/code-review/scripts/review-read.sh to view the latest review
    • Shows issues, suggestions, and code quality feedback
  4. Address issues: Fix bugs, security issues, or code quality problems
  5. Re-review (optional): Run ada::review:task again to verify fixes
  6. Finalize: Run ada::agent:finalize to ensure code quality before committing

PR Mode Workflow

  1. Ensure branch is ready: Make sure all changes are committed
  2. Run review: Execute bash skills/code-review/scripts/review-run.sh pr
    • CodeRabbit compares branch against main
    • Reviews all changed files in the PR
  3. Read results: Run bash skills/code-review/scripts/review-read.sh to view the latest review
  4. Address issues: Fix all critical issues before merging
  5. Finalize: Run ada::agent:finalize and bash skills/docs-check/scripts/check-docs.sh to ensure completeness
  6. Clean up (optional): Run bash skills/code-review/scripts/review-cleanup.sh to remove old review files

Reading Review Results

Use bash skills/code-review/scripts/review-read.sh to display the most recent review:

  • Shows review content with issues and suggestions
  • Displays statistics (files reviewed, issues found)
  • Lists files that were reviewed

Examples

bash
# Task mode
bash skills/code-review/scripts/review-run.sh task
bash skills/code-review/scripts/review-read.sh

# PR mode
bash skills/code-review/scripts/review-run.sh pr
bash skills/code-review/scripts/review-read.sh

# Complete workflow
bash skills/code-review/scripts/review-run.sh task && bash skills/code-review/scripts/review-read.sh
bash skills/code-quality/scripts/finalize.sh agent
bash skills/docs-check/scripts/check-docs.sh

References

  • Documentation Guide - For when to document changes

Output

Review results are saved to .ada/data/reviews/ directory:

  • {type}-review-{timestamp}.md - Review content
  • {type}-review-{timestamp}.json - Metadata with statistics

Integration with Other Skills

  • Run ada::code-quality after review to ensure reviewed code meets quality standards
  • Run ada::docs:check after review to ensure documentation is updated with code changes
  • Use ada::pr-review to manage GitHub PR comments after CodeRabbit review

Best Practices

  • Run task reviews frequently during development
  • Run PR reviews before submitting PRs
  • Address review issues before finalizing
  • Use ada::review:cleanup periodically to manage disk space
  • Combine with ada::code-quality and ada::docs:check for complete workflow

Expand your agent's capabilities with these related and highly-rated skills.

LukasStrickler/ai-dev-atelier

resolve-pr-comments

Resolve bot review comments (CodeRabbit, Copilot, Gemini) on GitHub PRs using subagents. Use when: (1) User asks to 'review PR comments' or 'resolve PR comments', (2) User says 'work through PR N comments' or 'handle bot comments', (3) Need to triage CodeRabbit/Copilot/Gemini review comments, (4) Processing PR feedback at scale, (5) Want to see what's already fixed vs still pending. NOT for: creating PRs, reviewing code yourself, writing new reviews. Triggers: review PR comments, resolve PR comments, work through PR comments, handle bot comments, process CodeRabbit comments, triage PR feedback, fix PR review issues, resolve bot comments, pr comment resolver.

2 0
Explore
LukasStrickler/ai-dev-atelier

tdd

Strict Red-Green-Refactor workflow for robust, self-documenting code. Discovers project test setup via codebase exploration before assuming frameworks. Use when: (1) Implementing new features with test-first approach, (2) Fixing bugs with reproduction tests, (3) Refactoring existing code with test safety net, (4) Adding tests to legacy code, (5) Ensuring code quality before committing, (6) When tests exist but workflow unclear, or (7) When establishing testing practices in a new project. Triggers: test, tdd, red-green-refactor, failing test, test first, test-driven, write tests, add tests, run tests.

2 0
Explore
LukasStrickler/ai-dev-atelier

use-graphite

Manage stacked PRs with Graphite CLI (gt) instead of git push/gh pr create. Auto-detects Graphite repos and blocks conflicting commands with helpful alternatives. Use when: (1) About to run git push or gh pr create in a Graphite repo, (2) Creating a new branch for a feature, (3) Submitting code for review, (4) Large changes that should be split into reviewable chunks, (5) Hook blocks your git command and suggests gt equivalent. NOT for: repos not initialized with Graphite, git add/commit/status/log. Triggers: git push blocked, gh pr create blocked, create branch, submit PR, stacked PRs, split large PR, gt create, gt submit, graphite workflow.

2 0
Explore
LukasStrickler/ai-dev-atelier

git-commit

Write clear git commits with Conventional Commits format. Detects project conventions from history and config. Guides commit granularity. Use when: (1) Completing working code, (2) Code builds and tests pass, (3) Ready to save, (4) Before pushing, (5) After review feedback. Triggers: automatically when finishing commitable work that builds and passes tests.

2 0
Explore
LukasStrickler/ai-dev-atelier

image-generation

Generate, edit, and upscale AI images. Use when creating visual assets for apps, websites, or documentation. FREE Cloudflare tier for iterate generation (~96/day), Fal.ai for paid tiers. Four quality tiers (iterate/default/premium/max). Supports text specialists, multi-ref editing, SVG, background removal. Triggers: generate image, create image, edit image, upscale, logo, picture of, remove background.

2 0
Explore
LukasStrickler/ai-dev-atelier

code-quality

Run comprehensive code quality checks including TypeScript typecheck, ESLint linting, Prettier formatting, and Markdown validation. Auto-fixes formatting issues in agent mode or provides read-only checks for CI pipelines. Use when: (1) Before committing code changes, (2) In CI/CD pipelines for automated quality gates, (3) After making significant code changes, (4) When preparing code for review, (5) When ensuring code meets quality standards, (6) For type checking, linting, formatting, and markdown validation, (7) In pre-commit hooks, or (8) For automated quality gates before merging. Triggers: finalize, code quality, typecheck, lint, format, check code, quality check, run checks, pre-commit, before commit, CI checks, validate code.

2 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results