bmad-autopilot-skill
Autonomous BMAD development orchestration
Découvrez les skills Développement, comparez leurs dépôts et consultez leurs instructions.
Autonomous BMAD development orchestration
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Master orchestrator control for PR lifecycle management with multi-agent coordination
Convert Claude Code slash commands, skills, or agents into standalone CLI tools for Linux/Mac (Bash) and Windows (PowerShell). Use when user says "cli-ify", "make this a CLI", "convert to command line", or want...
Interactive code review walkthrough using tmux and nvim for pair programming style review. Use when reviewing changes, preparing for PR review, or walking through a diff with the user.
Enforces project documentation structure in docs/plans/ directories - research.md for facts, design.md for decisions, tasks.md for implementation, thoughts/ for explorations.
Monitors project documentation for status drift. Activates when completing tasks, finishing phases, or when status may be stale. Reminds to run /wb:update_status when needed.
Use when about to claim work is complete, fixed, passing, or done - requires running verification commands and confirming output before making any success claims. Evidence before assertions.
Use when implementing features, fixing bugs, or writing any production code - enforces RED-GREEN-REFACTOR cycle where tests must fail before writing implementation code. Activates before coding begins.
仕様(Why)と設計(How)を記録し、Living Documentation原則でコードと常に同期させる
FleetFlow(KDLベースのコンテナオーケストレーションツール)を効果的に使用するためのガイド
Rust製非同期Docker APIクライアント「Bollard」の使い方と実装パターン
Use GitLab CI/CD Matrix Expressions to create dynamic 1:1 dependencies between parallel matrix jobs. This simplifies pipeline configuration by avoiding the manual listing of every job combination in `needs`.
Analyzes CI/CD pipelines to identify common antipatterns (like slow feedback loops or sequential steps) and recommends best practice patterns (like build images, parallelization, and build-once-deploy-anywhere)...
Provides paths to cc-track utility scripts for validation, task completion, and git operations. Use when a cc-track command needs to run a script.
Go testing conventions and patterns. Use when writing tests, discussing coverage, or editing _test.go files. Triggers: test organization, black-box testing, table-driven tests, HTTP mocking, coverage criteria,...
Core Go development patterns and idioms. Use for package design, code organization, configuration patterns, interface definitions, or when editing .go files. Triggers: package structure, dependency hierarchy, i...
Describe when this skill should be invoked. Include: - Trigger keywords (e.g., authentication, API design) - File patterns (e.g., when editing *.go files) - Use cases (e.g., implementing login flows)
ImageMagick integration patterns for Go. Use when processing images, rendering documents, or integrating ImageMagick commands. Triggers: image processing, document rendering, magick command, image conversion, P...
Container and infrastructure patterns for Go applications. Use when working with Dockerfiles, external binaries, or deployment configuration. Triggers: containerization, external binary integration, dependency...
Describe when this skill should be invoked. Include trigger keywords, file patterns, and explicit use cases. The more specific, the better Claude can determine when to load this skill.
Go library development patterns. Use when designing library APIs, implementing extensibility, or working on packages in pkg/ directories. Triggers: format extensibility, provider separation, capability composit...
HTTP API development patterns for Go. Use when creating endpoints, handlers, middleware, or error responses. Triggers: API design, HTTP handlers, error handling, functional options, option merging, response for...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.