code-review
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 6
- Forks
- 3
01 前言 Front Matter
- name
- code-review
- description
- Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
02 资源文件 5
- 其他customize.toml1.6 KB
- 参考文档steps/step-01-gather-context.md6.3 KB
- 参考文档steps/step-02-review.md2.1 KB
- 参考文档steps/step-03-triage.md2.6 KB
- 参考文档steps/step-04-present.md6.1 KB
03 SKILL.md 正文
Code Review Workflow
Goal: Review code changes adversarially using parallel review layers and structured triage.
Your Role: You are an elite code reviewer. You gather context, launch parallel adversarial reviews, triage findings with precision, and present actionable results. No noise, no filler.
Conventions
- Bare paths (e.g.
checklist.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{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: python3 {project-root}/.stellar-build/scripts/resolve_customization.py --skill {skill-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:
{skill-root}/customize.toml- defaults{project-root}/.stellar-build/custom/{skill-name}.toml- team overrides{project-root}/.stellar-build/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
Load config from {project-root}/.stellar-build/bmm/config.yaml and resolve:
project_name,planning_artifacts,implementation_artifacts,user_namecommunication_language,document_output_language,user_skill_leveldateas system-generated current datetimesprint_status={implementation_artifacts}/sprint-status.yamlproject_context=**/project-context.md(load if exists)- CLAUDE.md / memory files (load if exist)
- 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. Begin the workflow below.
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
- READ COMPLETELY: Read the entire step file before acting
- FOLLOW SEQUENCE: Execute sections in order
- WAIT FOR INPUT: Halt at checkpoints and wait for human
- 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
04 同仓库更多 Skills
zk-proofs
Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.
tyler-architect
System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.
stellar-help
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
stellar-competitive-landscape
Map the competitive landscape for a Stellar project idea. Use when a user says "who are my competitors on Stellar", "competitive analysis Stellar", "what already exists in this space on Stellar", "show me similar Stellar projects", "is anyone else building this on Stellar", or "map the Stellar landscape for X". Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.
standards
Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.
smart-contracts
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory - development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" - Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.