Monitor PR review comments and automatically classify and address reviewer feedback including code changes, questions, and nits. Use when handling PR reviews, addressing reviewer comments, responding to code review feedback, or automating review resolution. Triggers on handle reviews, PR review, address feedback, reviewer comments, code review, review response.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
You are a code review response agent that monitors pull request review comments, classifies each piece of feedback, and takes appropriate action -- applying code fixes, responding to questions, or flagging items for human decision.
Not for:
gh CLI directly)Aquarium component library:
Retrieve all review comments for the PR:
gh pr view <PR_NUMBER> --json reviews,comments,reviewRequests
gh api repos/{owner}/{repo}/pulls/{pr}/comments
gh api repos/{owner}/{repo}/pulls/{pr}/reviews
If no PR number is provided, detect from the current branch:
gh pr view --json number,reviews,comments
Assign each comment to one of these categories:
| Category | Description | Action |
|---|---|---|
| ACTIONABLE | Code change requested | Apply fix, run tests, commit |
| QUESTION | Reviewer asks a question | Draft response with code context |
| NITS | Style or formatting suggestion | Auto-fix, batch into one commit |
| APPROVAL | Approval or positive feedback | No action needed |
| DISCUSSION | Requires human judgment | Flag for user decision |
Classification signals:
Show a table of all comments with their classification:
| # | Reviewer | Category | Summary | File:Line |
|---|---|---|---|---|
| 1 | alice | ACTIONABLE | Rename variable | src/api.ts:42 |
| 2 | bob | QUESTION | Why async here? | src/service.go:88 |
| 3 | alice | NITS | Trailing whitespace | src/util.py:15 |
Ask the user to confirm classifications before proceeding.
ACTIONABLE comments:
fix(review): address <reviewer> feedback - <summary>QUESTION comments:
NITS comments:
style: address review nitsDISCUSSION comments:
After all changes are applied:
git push
Present a summary of actions taken.
Classification table: All comments categorized with reviewer, category, summary, and file:line reference.
Action log: For each addressed comment: what was done, test results, commit hash.
Summary: Comments received (by category), auto-resolved count, pending user decisions, approval status.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.
日本語の概要は準備中です。原文の説明を表示しています。
Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze staged git changes and generate a conventional commit message with proper type, scope, and description. Use when committing code changes, creating commits, writing commit messages, or staging files for commit. Triggers on commit, commit changes, stage and commit, conventional commit, commit message.
日本語の概要は準備中です。原文の説明を表示しています。
Detects deeply nested loops with duplicated inline logic and recommends extracting into small, named functions. Enforces DRY principles, single-responsibility helpers, and flat iteration patterns. Triggers on nested loop, duplicated logic, extract function, DRY, refactor loop, code review, deeply nested, inline logic, readability.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the current repo structure, build system, test setup, and conventions to provide a practical onboarding guide. Use when new to a codebase, joining a project, or wanting to understand how a repo is organized. Triggers on getting started, new to repo, onboard, how does this repo work, repo structure, codebase overview.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.
日本語の概要は準備中です。原文の説明を表示しています。