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

log-bitcoin-issues skill

safe

This skill audits Bitcoin integration via /check-bitcoin and creates prioritized GitHub issues for findings, avoiding duplicates and guiding fixes.

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.
effort: medium
---

# /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 creates GitHub issues for every finding, organized by priority. It flags security and reliability gaps without making code changes. Use it to convert audit results into actionable work items so teams can triage and track fixes.

How this skill works

It invokes the /check-bitcoin primitive to produce structured findings, then groups them by priority (P0–P3). The skill checks open GitHub issues labeled domain/bitcoin to avoid duplicates and creates new issues with a consistent title, labels, and a structured body describing problem, impact, location, and suggested fix. Each created issue includes a reference that the tool generated it.

When to use it

After running automated or manual Bitcoin integration checks
When you need a tracked backlog of security and reliability gaps
Before releases or audits to ensure issues are captured for remediation
When multiple teams need consistent, prioritized work items
To convert findings into GitHub workflow items for triage and assignment

Best practices

Run /check-bitcoin first so findings are structured and complete
Review existing open issues to avoid noisy duplicates before creating new ones
Use the provided priority mapping to ensure urgent security items become high-priority issues
Add precise file:line locations and reproduction steps in the issue body when available
Link the issue to remediation tasks (or /fix-bitcoin) to speed resolution

Example use cases

Detect and log a committed private key as a P0 GitHub issue for immediate rotation and remediation
Create P1 issues for missing reorg or double-spend handling identified by the audit
Capture missing monitoring and alerts as P2 issues so SRE can add metrics and alerts
List advanced feature gaps (RBF/CPFP/PSBT) as P3 enhancement issues for roadmap planning
Run before release to ensure confirmed-check and network-mismatch gaps are tracked

FAQ

Will this skill fix issues automatically?

No. This skill only creates GitHub issues describing findings. Use /fix-bitcoin to apply automatic or guided fixes.

How does it prevent duplicate issues?

It lists open GitHub issues with the domain/bitcoin label and matches titles and key metadata before creating new issues to avoid duplicates.