bmad-code-review
/bmad-code-review
Przegląda zmiany w kodzie kilkoma niezależnymi recenzentami równolegle, a potem sortuje i przedstawia ustalenia.
- Autor
- ph1996-cn ↗
- Repozytorium
- dsh-BMAD-Method ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 10
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przegląda zmiany w kodzie kilkoma niezależnymi recenzentami równolegle, a potem sortuje i przedstawia ustalenia.
Wyzwalacze z opisu
Oryginalny opis (EN)
Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code
Jak działa
- Conventions
- On Activation
- WORKFLOW ARCHITECTURE
- FIRST STEP
Podgląd SKILL.md
---
name: bmad-code-review
description: 'Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code"'
---
# Code Review Workflow
**Goal:** Review code changes adversarially. No noise, no filler.
Subagents, when the capability is available, are an important part of this workflow. Use them as directed by the workflow steps.
If you need an explicit user instruction to run them, ask once now for the whole workflow run.
## Conventions
- Bare paths (e.g. `checklist.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}`-prefixed paths resolve from the project working directory.
- `{skill-name}` resolves to the skill directory's basename.
## On Activation
### Step 1: Resolve the Workflow Block
Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`
**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
1. `{skill-root}/customize.toml` — defaults
2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
### Step 2: Execute Prepend Steps
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
### Step 3: Load Persistent Facts
Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
### Step 4: Load Config
Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
- `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
- `date` as system-generated current datetime
- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
- `project_context` = `**/project-context.md` (load if exists)
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Step 5: Greet the User
Greet `{user_name}`, speaking in `{communication_language}`.
### Step 6: Execute Append Steps
Execute each entry in `{workflow.activation_steps_append}` in order.
Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
## WORKFLOW ARCHITECTURE
This uses **step-file architecture** for disciplined execution:
- **Micro-file Design**: Each step is self-contained and followed exactly
- **Just-In-Time Loading**: Only load the current step file
- **Sequential Enforcement**: Complete steps in order, no skipping
- **State Tracking**: Persist progress via in-memory variables
- **Append-Only Building**: Build artifacts incrementally
### Step Processing Rules
1. **READ COMPLETELY**: Read the entire step file before acting
2. **FOLLOW SEQUENCE**: Execute sections in order
3. **WAIT FOR INPUT**: Halt at checkpoints and wait for human
4. **LOAD NEXT**: When directed, read fully and follow the next step file
### Critical Rules (NO EXCEPTIONS)
- **NEVER** load multiple step files simultaneously
- **ALWAYS** read entire step file before execution
- **NEVER** skip steps or optimize the sequence
- **ALWAYS** follow the exact instructions in the step file
- **ALWAYS** halt at checkpoints and wait for human input
## FIRST STEP
Read fully and follow: `./steps/step-01-gather-context.md`
Pliki w paczce (10)
- SKILL.md 4 KB
- customize.toml 5 KB
- references/claims-check.md 1 KB
- references/deletion-check.md 1 KB
- review-prompts/edge-case-hunter.md 8 KB
- review-prompts/verification-gap.md 10 KB
- steps/step-01-gather-context.md 8 KB
- steps/step-02-review.md 3 KB
- steps/step-03-triage.md 5 KB
- steps/step-04-present.md 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · ph1996-cn/dsh-BMAD-Method | 90 | MIT |
| bmad-code-org/BMAD-METHOD | 92 | MIT |
| drak905/Drake-Trainer | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 722531abbd0a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100bmad-developer
Obsługuje implementację w BMAD: dostarcza przetestowany kod ze specyfikacji historyjek poleceniami bmad:dev-story i bmad:code-review. - 100review
Ocenia diff albo fragment istniejącego kodu bez zmieniania go, z dowodami i niezależnymi recenzentami, gdy to potrzebne. - 100code-review
Przegląda zmiany w kodzie C pod kątem poprawności, bezpieczeństwa i stylu. - 90gds-code-review
Przegląda zmiany w kodzie od strony krytycznej, równolegle w kilku warstwach, i porządkuje uwagi w kategorie do działania. - 100bmad-architect
Obsługuje architekturę w BMAD: tworzy projekt systemu i sprawdza pokrycie wymagań poleceniami bmad:architecture i bmad:gate-check. - 100code-review
Przegląda zmiany w kodzie z niezależnej perspektywy pod kątem jakości, poprawności, bezpieczeństwa i utrzymywalności.