Development
log-lightning-issues - Claude MCP Skill
Run /check-lightning, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-lightning instead if you want to fix issues immediately.
SEO Guide: Enhance your AI agent with the log-lightning-issues tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to run /check-lightning, then create github issues for all findings. issues are created with priority l... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# /log-lightning-issues
Run Lightning integration audit and create GitHub issues for all findings.
## What This Does
1. Invoke `/check-lightning` to audit Lightning 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-lightning` to fix issues.
## Process
### 1. Run Primitive
Invoke `/check-lightning` skill to get structured findings.
### 2. Check Existing Issues
```bash
gh issue list --state open --label "domain/lightning" --limit 50
```
### 3. Create Issues
For each finding:
```bash
gh issue create \
--title "[P0] LND macaroon hardcoded" \
--body "$(cat <<'EOF'
## Problem
LND macaroon is committed to repo. Full node control risk.
## Impact
- Attacker can control node
- Funds theft possible
- Channel state manipulation risk
- Compliance breach
## Location
`config/lightning.ts`
## Suggested Fix
Run `/fix-lightning` or manually move to env:
```typescript
const macaroonHex = process.env.LND_MACAROON_HEX!;
```
---
Created by `/log-lightning-issues`
EOF
)" \
--label "priority/p0,domain/lightning,type/bug"
```
### 4. Issue Format
**Title:** `[P{0-3}] Lightning issue description`
**Labels:**
- `priority/p0` | `priority/p1` | `priority/p2` | `priority/p3`
- `domain/lightning`
- `type/bug` | `type/enhancement` | `type/chore`
**Body:**
```markdown
## Problem
What's wrong with Lightning integration
## Impact
Business/security/user impact
## Location
File:line if applicable
## Suggested Fix
Code snippet or skill to run
---
Created by `/log-lightning-issues`
```
## Priority Mapping
| Gap | Priority |
|-----|----------|
| Macaroon or seed in repo | P0 |
| RPC exposed without TLS | P0 |
| Missing macaroon auth | P0 |
| No invoice settlement verification | P1 |
| No payment timeout handling | P1 |
| No fee caps | P1 |
| No idempotency for payment requests | P2 |
| Missing retry/backoff | P2 |
| Monitoring/alerts missing | P2 |
| Advanced routing features | P3 |
## Output
After running:
```
Lightning Issues Created:
- P0: 2 (macaroon, TLS)
- P1: 2 (settlement checks, timeouts)
- P2: 3 (idempotency, retries, alerts)
- P3: 1 (routing features)
Total: 8 issues created
View: gh issue list --label domain/lightning
```
## Related
- `/check-lightning` - The primitive (audit only)
- `/fix-lightning` - Fix Lightning issues
- `/lightning` - Full Lightning lifecycle
- `/lightning-health` - Node diagnostics
- `/groom` - Full backlog groomingSignals
Information
- Repository
- phrazzld/claude-config
- Author
- phrazzld
- Last Sync
- 3/2/2026
- Repo Updated
- 3/1/2026
- Created
- 1/28/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build-scrape
Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
Related Guides
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Mastering VSCode Extension Development with Claude: A Complete Guide to the TypeScript Extension Dev Skill
Learn how to use the vscode extension dev typescript Claude skill. Complete guide with installation instructions and examples.
Next.js SEO Dev: The Essential Claude Skill for Documented React Development
Learn how to use the nextjs seo dev Claude skill. Complete guide with installation instructions and examples.