review

Alias for /code-review. Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature.

Jump to install Review files

Repository: bdfinst/agentic-dev-team
Last source activity: July 7, 2026 at 20:53
Detected SKILL.md language: English
Stars: 299
Forks: 36

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/bdfinst/agentic-dev-team/tree/main/plugins/dev-team/skills/review.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/bdfinst/agentic-dev-team --skill review

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name: review
description: Alias for /code-review. Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature.
argument-hint: [--agent <name>] [--since <ref>] [--path <dir>] [--all] [--json] [--internal] [--force --reason "<text>"] [--static-analysis|--no-static-analysis] [--init-risks] [--background]
user-invocable: true
allowed-tools: Read, Write, Edit, Grep, Glob, AskUserQuestion, Agent, Bash(git diff *), Bash(npx *), Bash(npm run *), Bash(pnpm *), Bash(yarn *), Bash(tsc *), Bash(eslint *), Bash(git log *), Bash(gh run *), Bash(semgrep *), Bash(ruff *), Bash(mypy *), Skill(review-agent *)

# Review (alias) Role: orchestrator. ## Orchestrator constraints 1. Pure alias — change no behavior. 2. Pass all arguments through to /code-review unchanged. 3. **Be concise.** Defer all output to code-review.md. This is an alias for `/code-review`. Read and follow `skills/code-review/SKILL.md` with all arguments passed through. > **Keep frontmatter in sync.** This alias delegates the entire `/code-review` > flow, so its `allowed-tools` and `argument-hint` MUST mirror > `skills/code-review/SKILL.md`. `allowed-tools` is an allowlist — omitting a tool > the canonical command needs (e.g. `Edit` for the fix loop, `AskUserQuestion` > for the fix/report prompt, `Bash(ruff *)` for Python lint) silently breaks > that capability under `/review`. Arguments: $ARGUMENTS ## Steps ### 1. Pass through Read and follow `skills/code-review/SKILL.md` with `$ARGUMENTS` unchanged.

View on GitHub

Back to search Back to installation

adr-tools

Create and manage Architecture Decision Records using the npryce adr-tools CLI. Use when the user asks to "add an ADR", "record this decision", "create an ADR", "supersede ADR N", "link ADRs", "generate the ADR table of contents", or any request involving the `adr` command. Pairs with the adr-author agent — this skill is the mechanics (commands, files, links); adr-author is the decision framework (when an ADR is warranted) and the prose authoring.

2026-10-03

design-doc

Produce a written design document in docs/specs/ with user approval before planning begins. Use this skill during the Research phase when a feature request, architectural change, or non-trivial task enters the pipeline. Ensures misunderstandings are caught before any planning or implementation work starts. Also use when the user says "brainstorm", "design", "spec", or "let's think through this".

2026-10-03

specs

Collaborative workflow for producing the three specification artifacts (intent, architecture notes, acceptance criteria) that describe a change and its goals before any implementation begins. Its value is resolving ambiguity with a human before build starts — not synthesizing edge cases. Use when starting any new feature or behavior change — do not write code until artifacts pass the consistency gate. BDD/Gherkin scenarios are authored later, per slice, in /plan.

2026-10-03

View all from this repository

review

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository