bug-workflow
v4.0.3by mark22013333 · author: Cheng
Bug 工作流: 涵蓋建立、調查、修復、驗證、結案與知識沉澱。
What bug-workflow does, in the publisher's words
跨 Host 的 Bug lifecycle:建立狀態、蒐集證據、驗證根因、修復、回歸測試,最後由 Human UAT 決定是否結案。核心流程依賴 CREW Host Capability Contract,而不是某一家的 agent/team 工具。
首次使用可執行 /bug-setup,或由 /crew-init 統一引導。
推薦:
- /bug-start 自動使用 intake refinement;/bug-investigate 會先進 /bug-start。
- 已存在的 Bug、/bug-investigate --resume、/bug-update、/bug-fix、/bug-close 不重新 refine。
- Host 支援 named sub-agent 時使用 bug-intake-refiner;不支援時 inline 執行同一 shared contract。
- Human confirmation 前禁止 Notion/state/.spec side effect。
- confirmation 後、持久化前做 credential preflight;疑似 secret 必須先由 Human 提供 redacted 版本。
- 在 Git repo 內寫 cache/state 前先確認.spec/ 已被.gitignore 保護。
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 10
- MCP servers
- 0
- Stars
- 9
- License
- MIT
- Repo created
- 2026-03-11
- Last pushed
- 2026-10-04
- Publisher type
- User
- Version
- 4.0.3
Links
Skills · 10
- bug-close
- bug-fix
- bug-investigate
- bug-setup
- bug-start
- bug-update
- crew-doctor
- crew-init
- crew-upgrade
- project-add
Category
Other. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
sdlc · bug · workflow · debugging · bug-tracking · knowledge-base
Related by publisher and keywords
功能開發工作流: 以.spec/ 做本地規劃,涵蓋需求、DB、架構、實作、驗證、審查與結案。
让 AI Agent 直连 Workflow(workflow.games):本地优先规划与拆解需求、自动查重和补全依赖、按权限模式受控并发上传、规划需求与需求室、记 bug、查任务、拿单执行与证据回写、跨仓库交接纪要、线上 QA 验收、查文档、经确认后向平台方匿名反馈问题与建议
사용자 의도를 먼저 판별하고, 제품·기능·연구 실험·버그에 맞는 서로 다른 승인 흐름을 적용하는 한국어 워크플로우입니다.
Workflow rules from CLAUDE.md turned into hooks and skills that actually fire
End-to-end AI-Driven Development Lifecycle workflow: Inception, Construction, Integration, and fast-path bug fixes, with human approval gates at every stage.
The Moe skill library: brainstorming, planning, TDD, systematic debugging, code review, worktrees, parallel dispatch, plugin authoring, and more.
[](https://agentpluginsdirectory.com/plugins/bug-workflow)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.