菜单
Assess an existing doppelganger issue (explore codebase, identify scope/risks/ambiguities, post assessment) or create a new structured issue. Usage: dg-issue 42 (assess) or dg-issue (create) or dg-issue <description> (create with context)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pre-merge checks, version bump, create PR/MR. Version bump happens BEFORE merge (on the feature branch) because master requires PRs. Usage: dg-publish
Explore codebase, create implementation plan, create feature branch, create doppelganger(dg) branch, post plan as dg branch comment. Everything lives on the dg branch from this point forward. Usage: dg-plan 42
Commit changes, and post a progress comment in doppelganger(dg). Stages files by name (never git add -A), matches existing commit style. Usage: dg-commit [optional commit message]
Run specialized review agents in parallel on a doppelganger(dg) branch (code-reviewer, error-auditor, test-reviewer, completeness-checker, simplifier), write findings, then independently assess each finding to separate genuine issues from nitpicks and false positives. Usage: dg-review [aspects]
Implement a plan from a doppelganger(dg) branch, or fix review findings. Usage: dg-implement [finding-numbers]
| name | dg-issue |
| description | Assess an existing doppelganger issue (explore codebase, identify scope/risks/ambiguities, post assessment) or create a new structured issue. Usage: dg-issue 42 (assess) or dg-issue (create) or dg-issue <description> (create with context) |
| argument-hint | [issue-number | description] |
User input: $ARGUMENTS
dg so any future session can pick up context.<!-- dg-assessment -->, <!-- dg-plan -->, <!-- dg-review -->, <!-- dg-progress --> as the first line of comment bodies for reliable discovery.git add -A or git add .. Stage files by name. Never stage secrets (.env, credentials, tokens, keys).update_task tool to show progress through multi-step commands.If the input is a number, run ASSESS mode. Otherwise, run CREATE mode.
Assess an existing doppelganger issue — explore the codebase, identify scope/risks/ambiguities, post assessment.
dg issue read <number>
Parse: problem statement, constraints, requirements, acceptance criteria, existing comments.
Update task: read → completed, explore → in_progress.
Launch 2 Explore subagents in parallel targeting different aspects. Use the implement role for these agents. If there isn't an implement role configured, then they can just use default.
Each agent should return 5-10 key files. After agents complete, read all identified files.
Update task: explore → completed, assess → in_progress.
Present to the user:
Post as an issue comment:
cat > /tmp/dg-comment.md << 'DG_EOF'
<!-- dg-assessment -->
## Issue Assessment
<assessment content>
---
*Automated assessment by doppelganger*
DG_EOF
dg issue comment <number> < /tmp/dg-comment.md
Update task: post → completed.
Suggest next step: /skill:dg-plan <number>
Create a new structured GitHub issue from context or description.
If a description was provided, use it as the starting point. Otherwise, ask the user what they want to create an issue for.
Explore the codebase if needed to understand the relevant area.
Create a structured issue with:
Present the draft to the user for approval.
cat > /tmp/dg-body.md << 'DG_EOF'
<body>
DG_EOF
dg issue create --name "<title>" < /tmp/dg-body.md
Report the issue number and URL. Suggest next step: /dg-plan <number>