菜单
Bug investigation sub-agent. Receives triage context from the workflow manager, investigates codebase for root cause, and generates a draft bug spec. Dispatched by the manager after triage — do not invoke directly.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/opsMachine/OM-Agency --skill diagnose命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | diagnose |
| description | Bug investigation sub-agent. Receives triage context from the workflow manager, investigates codebase for root cause, and generates a draft bug spec. Dispatched by the manager after triage — do not invoke directly. |
| allowed-tools | Read, Grep, Glob, Bash, WebFetch, gh |
| contract | {"tags":["bug","diagnosis","investigation"],"state_source":"github_issue","inputs":{"params":[{"name":"issue_number","required":false},{"name":"actual_behavior","required":true},{"name":"expected_behavior","required":true},{"name":"reproduction_steps","required":false},{"name":"started_when","required":false},{"name":"environment","required":false}],"gates":[]},"outputs":{"mutates":[{"field":"status","sets_to":"Approved"}],"side_effects":["Creates bug spec in Documents/specs/"]},"next":["plan-tests","implement-direct"],"human_gate":false} |
Autonomous bug investigation. Receives triage context from the workflow manager (who already gathered details from the human and read the GitHub issue), investigates the codebase, identifies root cause, and generates a draft bug spec.
You are a sub-agent. Do NOT ask the user questions. All context is in your prompt.
The workflow manager dispatches you after completing bug triage:
Read the triage context from your prompt. You should have:
If the issue is tracked, read the full issue for additional context:
gh issue view <number> --json title,body,comments,labels
Search the codebase:
git log -p --since="2 weeks ago" -- <file>Identify:
If security-relevant, flag for extra review in your findings.
Create a spec file so downstream skills have a contract to work from.
File path: Documents/specs/{issue-number}-{slug}-spec.md
Documents/specs/bug-{slug}-spec.md42-email-missing-replyto-spec.mdUse this template — fill from your investigation:
# Bug: {title}
**Issue:** #{number}
**Status:** Approved
**Created:** {YYYY-MM-DD}
## Problem Statement
**Actual:** {what's happening}
**Expected:** {what should happen}
**Root cause:** {where and why, from Step 2}
## Acceptance Criteria
Write criteria specific enough that an implementer can assess ✅/⚠️/❌ against each one.
Avoid vague phrasing — say exactly what should happen.
| # | Criterion | Test Type |
|---|-----------|-----------|
| 1 | {specific: e.g. "Clicking Save with empty name shows 'Name required' error"} | Unit \| Integration |
| 2 | {specific: e.g. "Email sends successfully when replyTo matches an auth.users record"} | Unit \| Integration |
| 3 | {regression: e.g. "Existing quotes still load correctly after migration"} | Unit \| Integration \| Manual |
## Non-Goals
- Not refactoring {related area} beyond the fix
- {other explicit exclusions}
## Security Considerations
- **Impact:** {from Step 3 — "none" is fine if not security-relevant}
## Technical Notes
**Files involved:** {from Step 2}
- `{file}` — {what's wrong and what needs to change}
**Reproduction:** {steps to trigger the bug}
Key differences from feature specs:
Approved immediately (diagnosis IS the review)Report back to the manager with:
End-of-skill check: See
shared/primitive-updates.md. Signals: gotchas discovered, non-obvious system behavior, domain terms encountered.
Performs comprehensive, brutally honest full-codebase review as a grumpy but fair senior developer with 20+ years of experience. Use when the user asks for a grumpy dev code review, brutal code review, senior dev review, comprehensive codebase audit, hall-of-shame code smells, or a gut-check on the entire project (not just a PR diff).
Diagnose and fix OneCLI gateway issues — Docker not running, 407 proxy auth, 401 from API (MITM not active), stale aoc_ token, CA cert refresh, secret setup, version pinning. Use when onecliStart fails, update-fathom-db fails, proxy returns 407 or 401, mode=tunnel in logs, or after OneCLI container recreation.
ANY CRM or progress.md write, log call, add contact, pipeline lookup, paste transcript/email. Runs lifecycle routing in Step 0 — delivery work goes to progress.md not Won CRM Next Action. Query before create. For week view use week-scan not this skill. OM-Repo SKILLS-MAP.md.