원클릭으로
create-issue
Create a GitHub issue for vultisig-ios using bug/feature templates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Create a GitHub issue for vultisig-ios using bug/feature templates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Implement UI from Figma designs via MCP with a closed-loop pixel-parity check. Extract exact values (never eyeball), translate to SwiftUI, then render→diff→fix against the Figma export until it matches. Use when implementing or auditing UI against Figma.
HTTP networking layer reference — TargetType, HTTPClient, services, error handling.
Fetch CodeRabbit review comments from batch PRs and auto-fix the issues. Pushes fixes and re-requests review.
Run multiple tasks overnight as parallel PRs. Produces a PRD per task, selects skills/rules, spawns isolated agents, and reports PR links.
Run multiple tasks overnight as parallel PRs. Produces a PRD per task, selects skills/rules, spawns isolated agents, and reports PR links.
Run SwiftLint and xcodebuild to verify the project compiles cleanly.
| name | create-issue |
| description | Create a GitHub issue for vultisig-ios using 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: [iOS, macOS]
files:
read: []
write: []
verify: ["swiftlint lint"]
-->
# [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
- [ ] SwiftLint passes
- [ ] Build 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: [iOS, macOS]
files:
read: []
write: []
verify: ["swiftlint lint"]
-->
# [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
- [ ] SwiftLint passes
- [ ] Build 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 |
project.pbxproj directly — it is generated from VultisigApp/project.yml by XcodeGen. Change sources or project.yml and run make generate.Blockchain/Tss/ without explicit review"key".localized for all user-facing stringsgh issue create \
--repo vultisig/vultisig-ios \
--title "[Fix|Add] Short description [Area]" \
--label "bug|enhancement" \
--body "$(cat <<'EOF'
<full body from template above>
EOF
)"
Print the issue URL when done.