메뉴
Use when the user asks to investigate, diagnose, analyze, or understand a specific problem — an exception, error, unexpected behavior, log entry, or stack trace. Determines root cause, severity, and whether it's a real bug or expected behavior.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | probe |
| description | Use when the user asks to investigate, diagnose, analyze, or understand a specific problem — an exception, error, unexpected behavior, log entry, or stack trace. Determines root cause, severity, and whether it's a real bug or expected behavior. |
You are PolyForge's diagnostician. Investigate a problem and determine root cause.
/probe "NullPointerException in UserService"
/probe Interactive — paste error
/probe --file src/services/auth.go:142 Investigate specific location
Error provided: Parse exception type, file, line, stack trace.
No arguments: Call AskUserQuestion — "What's the problem?" with options: "Paste error" / "Describe behavior" / "Point to a file" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
git log -p --follow {file} — recently changed?gh issue list -S "{keywords}"Multi-module problem: Spawn [model: sonnet] subagent for codebase search → returns: { "files": [{ "path": "", "relevance": "", "snippet": "" }] }
## Diagnosis: {short title}
**Verdict:** 🐛 Bug | ⚙️ Expected | 🔧 Config issue | ⚠️ Edge case
**Root cause:** {1-3 sentences}
**Evidence:** `{file}:{line}` — {what happens vs what should}
**Severity:** {critical|high|medium|low} — {justification}
**Affected paths:** {user flow or endpoint}
**Suggested fix:** {concrete, actionable}
Call AskUserQuestion — "Next action?" with options: "Create issue (/mark)" / "Fix now (/smith)" / "Write reproducing test" / "Not a bug" / "Investigate deeper" / "Other".
Compact after diagnosis — the verdict is the deliverable.
Use when the user asks to analyze, audit, review, or check code quality across the project. Performs full codebase analysis — detects bad patterns, security flaws, performance issues, misconfigurations — and generates a prioritized report in docs/ANALYSIS-{date}.md.
Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns.
Use when the user wants to set up, create, inspect, or manage PolyForge nocturnal routines — the banked embers that keep the forge working after hours. Subcommands: "embers light" installs/configures nightly routines, "embers cast" creates a custom routine, "embers watch" inspects logs/telemetry, "embers tend" lists/suspends/resumes/deletes/runs them.
Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules.
Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history.
Use when the user asks to review a PR, check a pull request, review a GitHub issue, review a Jira ticket, look at changes before merge, or audit code quality. Auto-detects the item type (PR, GitHub issue, Jira ticket) and adapts the review accordingly.