oliver-kriska/phx:compound
plugins/elixir-phoenix/skills/compound/SKILL.md
Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
$ install --global
skillsauthnpx skillsauth add oliver-kriska/claude-elixir-phoenix phx:compoundInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 17, 2026, 6:05 AM222.2s2 files scanned
SKILL.md
- name:
- phx:compound
- description:
- Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
- effort:
- low
- argument-hint:
- [description of what was fixed]
Compound — Capture Solutions as Knowledge
After fixing a problem, capture the solution as searchable institutional documentation.
Usage
/phx:compound Fixed N+1 query in user listing
/phx:compound Resolved LiveView timeout in dashboard
/phx:compound # Auto-detects from recent session context
Philosophy
Each unit of engineering work should make subsequent units easier — not harder.
Workflow
Step 1: Detect Context
- If
$ARGUMENTSprovided, use as description - If no args, check scratchpad DEAD-END/DECISION entries,
git diff,.claude/plans/{slug}/progress.mdfor recent completions - If unclear, ask: "What problem did you just solve?"
Only document non-trivial problems that required investigation.
Step 2: Search Existing Solutions
Create .claude/solutions/ directory if it doesn't exist (run mkdir -p .claude/solutions).
Then search .claude/solutions/ for relevant keywords using Grep.
If found: Create new (different root cause), Update existing (same root cause, new symptom), or Skip.
Step 3: Gather Details and Create Solution
Extract from session context: module, symptoms, investigation steps, root cause, solution code, and prevention advice.
Validate frontmatter against compound-docs/references/schema.md,
then create file using compound-docs/references/resolution-template.md.
Step 4: Decision Menu
- Continue (default)
- Promote to Iron Law check — Add to iron-law-judge
- Update skill reference — Add to relevant skill
- Update CLAUDE.md — Add prevention rule
Auto-Trigger Phrases
When user says "that worked", "it's fixed", "problem solved",
"the fix was" — suggest /phx:compound.
Supply-chain finding auto-feed (Phase 3)
When /phx:deps-audit produces a BLOCK-severity finding that the
user investigates and confirms is a real malicious pattern (not a
false positive), suggest:
Caught a high-severity finding in
<pkg>@<version>. Run/phx:compoundto capture this for future audits?
If accepted, the resulting solution doc goes to
.claude/solutions/supply-chain/<pkg>-<cve_or_pattern>.md and
includes the exact rule-id + snippet + diff window that triggered
the finding. This compounds the audit corpus: future runs of
/phx:deps-audit grep solutions/supply-chain/ for snippet
matches and pre-elevate severity on known-bad patterns.
Always prompt; never auto-write. Solution docs are durable and shape future trust calls — the user reviews before committing.
Iron Laws
- YAML frontmatter validates or STOP
- Symptoms must be specific — not "it broke"
- Root cause is WHY, not WHAT
- One problem per file
- NEVER document a fix before verifying it works — run
mix compile && mix testfirst; unverified solutions poison the knowledge base
Integration with Workflow
/phx:review → Complete → /phx:compound ← YOU ARE HERE
│
.claude/solutions/{category}/{fix}.md
│
/phx:investigate and /phx:plan search here
References
${CLAUDE_SKILL_DIR}/references/compound-workflow.md— Detailed step-by-step- See also:
compound-docsskill for schema and templates
Related Skills
oliver-kriska/freeze
tools
VerifiedTrustedCommunity
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
425SKILL.mdUpdated Jun 9, 2026
oliver-kriska/ash-framework
development
VerifiedTrustedCommunity
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
425SKILL.mdUpdated Jun 9, 2026
oliver-kriska/phx:mix-compression
development
VerifiedTrustedCommunity
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
425SKILL.mdUpdated May 13, 2026
oliver-kriska/narrow-bare-rescue
development
VerifiedTrustedCommunity
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
425SKILL.mdUpdated Apr 25, 2026