home / skills / phrazzld / claude-config / log-bitcoin-issues

log-bitcoin-issues skill

This skill audits Bitcoin integration with /check-bitcoin and creates prioritized GitHub issues for findings to drive remediation.

npx playbooks add skill phrazzld/claude-config --skill log-bitcoin-issues

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.6 KB

---
name: log-bitcoin-issues
description: |
  Run /check-bitcoin, then create GitHub issues for all findings.
  Issues are created with priority labels and structured format.
  Use /fix-bitcoin instead if you want to fix issues immediately.
---

# /log-bitcoin-issues

Run Bitcoin integration audit and create GitHub issues for all findings.

## What This Does

1. Invoke `/check-bitcoin` to audit Bitcoin integration
2. Parse findings by priority (P0-P3)
3. Check existing issues to avoid duplicates
4. Create GitHub issues for each finding

**This is an issue-creator.** It creates work items, not fixes. Use `/fix-bitcoin` to fix issues.

## Process

### 1. Run Primitive

Invoke `/check-bitcoin` skill to get structured findings.

### 2. Check Existing Issues

```bash
gh issue list --state open --label "domain/bitcoin" --limit 50
```

### 3. Create Issues

For each finding:

```bash
gh issue create \
  --title "[P0] Hot wallet key stored in repo" \
  --body "$(cat <<'EOF'
## Problem
Bitcoin hot wallet private key committed in repo. Critical loss risk.

## Impact
- Funds theft
- Full wallet compromise
- Irreversible loss

## Location
`config/bitcoin.ts`

## Suggested Fix
Run `/fix-bitcoin` or move key to secret store and rotate.

---
Created by `/log-bitcoin-issues`
EOF
)" \
  --label "priority/p0,domain/bitcoin,type/bug"
```

### 4. Issue Format

**Title:** `[P{0-3}] Bitcoin issue description`

**Labels:**
- `priority/p0` | `priority/p1` | `priority/p2` | `priority/p3`
- `domain/bitcoin`
- `type/bug` | `type/enhancement` | `type/chore`

**Body:**
```markdown
## Problem
What's wrong with Bitcoin integration

## Impact
Business/security/user impact

## Location
File:line if applicable

## Suggested Fix
Code snippet or skill to run

---
Created by `/log-bitcoin-issues`
```

## Priority Mapping

| Gap | Priority |
|-----|----------|
| Private key in code/repo | P0 |
| No confirmation checks | P0 |
| Wrong network (mainnet/testnet) | P0 |
| Address reuse | P1 |
| No reorg handling | P1 |
| No double-spend/mempool checks | P1 |
| No fee estimation/bumping | P2 |
| Single node/provider dependency | P2 |
| Missing monitoring/alerts | P2 |
| Advanced features (RBF/CPFP/PSBT) | P3 |

## Output

After running:
```
Bitcoin Issues Created:
- P0: 2 (keys, confirmations)
- P1: 3 (reorg, reuse, mempool)
- P2: 3 (fees, redundancy, alerts)
- P3: 1 (advanced features)

Total: 9 issues created
View: gh issue list --label domain/bitcoin
```

## Related

- `/check-bitcoin` - The primitive (audit only)
- `/fix-bitcoin` - Fix Bitcoin issues
- `/bitcoin` - Full Bitcoin lifecycle
- `/bitcoin-health` - Node and webhook diagnostics
- `/groom` - Full backlog grooming

Overview

This skill runs a Bitcoin integration audit and automatically files GitHub issues for each finding. It categorizes findings by priority (P0–P3), avoids duplicate issues by checking existing open tickets, and creates structured, labeled issues ready for triage. Use when you want to convert audit discoveries into tracked work items rather than immediate fixes.

How this skill works

The skill invokes the /check-bitcoin primitive to retrieve structured findings about the Bitcoin integration. It maps each finding to a priority, checks open GitHub issues with the domain/bitcoin label to prevent duplicates, and creates new issues with a standardized title, labels, and a structured body describing the problem, impact, location, and suggested fix. Issue labels follow priority/domain/type conventions so you can filter and assign work easily.

When to use it

After running a Bitcoin integration audit to convert findings into tracked issues
When preparing a backlog of security and reliability tasks for Bitcoin infrastructure
Before a sprint planning or grooming session to populate issues for triage
When you want audit findings recorded but prefer manual fixes or review
If you need clear, repeatable issue templates for security and operational gaps

Best practices

Run /check-bitcoin first to produce structured findings the skill expects
Limit issue creation rate by reviewing P0 findings immediately for emergency response
Ensure the GitHub token has permission to list and create issues in the target repo
Use consistent assignees or teams for domain/bitcoin so issues land with the right owners
Review newly created issues for required context (logs, repro steps) and attach artifacts if needed

Example use cases

Automate backlog creation after a security sweep that checks keys, confirmations, and network config
Create a prioritized list of operational improvements after node diagnostics reveal missing monitoring
Record duplicate-free issues for a post-incident review where several Bitcoin gaps were found
Generate work items for engineering to implement advanced features like RBF/CPFP/PSBT later in the roadmap
Convert audit output into triage-ready tasks before a vulnerability remediation sprint

FAQ

Will this skill fix the issues it creates?

No. This skill only creates issues. Use /fix-bitcoin if you want automated fixes applied immediately.

How does it avoid duplicate issues?

It lists open issues labeled domain/bitcoin and compares titles and problem locations before creating a new issue to reduce duplicates.

How are priorities assigned?

Findings from /check-bitcoin are mapped to P0–P3 based on severity (e.g., keys in repo or wrong network are P0; missing fee bumping is P2).