Menu
Create a GitHub issue for vultisig-windows using the official bug/feature templates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Address CodeRabbit or other reviewer comments on a PR to make it merge-ready.
God-mode orchestrator. Takes a Linear ticket OR PR and handles the ENTIRE workflow end-to-end โ branch creation, implementation, testing, commits, PR creation, Linear updates, OR exhaustive PR review with parallel agents. Use for complete feature delivery or deep PR audits.
Approve and merge a GitHub PR. Use when you want to approve and merge the current branch's PR, or a specific PR number.
Comprehensive testing guide covering unit, integration, and E2E tests. Reference for deciding what to test and how, with Vitest and Playwright patterns.
Search and analyze feature implementations in sibling iOS, Android, and backend repositories. Use when porting features or validating cross-platform parity.
Stage, commit, and optionally push changes. Use after completing a task.
| name | create-issue |
| description | Create a GitHub issue for vultisig-windows using the official bug/feature templates. |
/create-issue โ infer everything from conversation context.
bug, title prefix: [Fix]<!-- AGENT
type: "bugfix"
priority: "critical|high|medium|low"
size: "tiny|small|medium"
platform: [windows, extension]
files:
read: []
write: []
verify: ["yarn check:all"]
-->
# [Fix] <what's broken> [<screen/area>]
## Problem
<!-- 2-3 sentences. What's broken? Who's affected? -->
## Expected Behavior
<!-- What should happen instead? -->
## Steps to Reproduce
1.
2.
3.
## Solution
<!-- 1 paragraph. WHAT to do and WHY this approach. Leave blank if unsure. -->
## Scope
### Must Do
- [ ] <!-- Specific fix 1 -->
- [ ] <!-- Specific fix 2 -->
### Must NOT Do
- Don't change unrelated code
- Don't refactor surrounding logic
## Acceptance Criteria
- [ ] `yarn check:all` succeeds
- [ ] <!-- Specific behavior check 1 -->
- [ ] <!-- Specific behavior check 2 -->
enhancement, title prefix: [Add]<!-- AGENT
type: "feature"
priority: "critical|high|medium|low"
size: "tiny|small|medium"
platform: [windows, extension]
files:
read: []
write: []
verify: ["yarn check:all"]
-->
# [Add] <what to build> [<screen/area>]
## Problem
<!-- 2-3 sentences. What's missing or suboptimal? -->
## Solution
<!-- 1 paragraph. WHAT to do and WHY this approach. -->
## Scope
### Must Do
- [ ] <!-- Specific deliverable 1 -->
- [ ] <!-- Specific deliverable 2 -->
### Must NOT Do
- Don't change existing behavior
- Don't add extra dependencies without approval
### Out of Scope
- <!-- Related but separate work โ future issue -->
## Acceptance Criteria
- [ ] `yarn check:all` succeeds
- [ ] <!-- Specific behavior check 1 -->
- [ ] <!-- Specific behavior check 2 -->
| Size | Files | Lines | Example |
|---|---|---|---|
tiny | 1 | <50 | Fix typo, update constant |
small | 1โ3 | 50โ200 | Fix a bug, add a function |
medium | 3โ8 | 200โ500 | New feature with tests |
large | 8+ | 500+ | SPLIT THIS |
lib/ is normal workspace code hereโedit when the issue requires it (not a copy of another repo)core/mpc/ or tss/ without explicit review approvalen.ts for translationsgh issue create \
--title "[Fix|Add] Short description [Area]" \
--label "bug|enhancement" \
--body "$(cat <<'EOF'
<full body from template above>
EOF
)"
Print the issue URL when done.