AI-driven, CLI-first dotfiles for Linux & macOS — chezmoi + mise, Fish, Neovim, and a custom Go CLI
Skill Claude CodeCodex
Reconstruct why tracked code exists from read-only Git history. Trace files, symbols, or lines through introducing commits or pull requests, rationale, reverts, renames, authorship, co-change clues, and issues.
Skill Claude CodeCodex
Audit a whole repository across architecture, source, tests, tooling, security, CI/CD, docs, and releases. Use for cross-cutting audits, readiness, or technical-debt reviews with ranked findings — not one diff or release candidate.
Skill Claude CodeCodex
Scan repositories with Trivy and gitleaks for vulnerabilities, IaC, secrets, licenses, images, and git history; triage concrete findings.
Skill Claude CodeCodex
Audit third-party Agent Skills/extensions for supply-chain security without running them before install/trust. Inspect scripts, hooks, MCP/plugins, hidden instructions, symlinks, credential/network flows, and provenance/licenses.
Skill Claude CodeCodex
Manage secrets with sops and age: commit encrypted files, decrypt only in memory, and wire Flux or OpenTofu runtimes.
Skill Claude CodeCodex
Diagnose unknown-cause bugs, test/build or auth failures, flakes, and runtime performance regressions. Investigate, reduce, localize, falsify hypotheses, and explain root cause before implementation.
Skill Claude CodeCodex
Publish source-grounded technical articles across draft, canonical site, export, and public verification. Not software releases or standalone documents.
Skill Claude CodeCodex
Verify unfamiliar framework APIs and architectures from exact local dependency source and current primary docs. Compare installed packages, specs, and versions before choosing an approach; return a recommendation with proof boundaries.
Skill Claude CodeCodex
Canonical infrastructure-as-code stack — OpenTofu-first with tflint, trivy config scans, terraform-docs, native tests, and GCS state. Use for any Terraform or OpenTofu work.
Skill Claude CodeCodex
Implement an isolated bug fix or behavior change with an honest red-green-refactor cycle. Use when a regression test should fail before the correction, or when tested logic, refactors, or seams must prove correctness.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: