Menu
Use when asked to audit configs, check config freshness, verify tool configs are up to date, or after upgrading nix flake inputs.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Shape answers so they are immediately actionable instead of long. Use on any response that would otherwise run long — multi-step tasks, explanations, plans, reviews with many findings, or answers that hand back commands, paths, or snippets to run. Leads with the next action, numbers steps, restates progress, caps lists, and gives concrete time estimates. Complements caveman (which handles tone); this handles shape.
Senior software architect for system design, ADRs, microservices evaluation, technology trade-off analysis. Use when designing system architecture, evaluating patterns, creating ADRs, analyzing technology choices, or planning migrations.
Go CLI development with Cobra command hierarchy, Bubbletea interactive TUI, Lipgloss terminal styling, Charmbracelet ecosystem (Bubbles, Huh forms, Glamour markdown rendering), and shell completions. Use when building CLI tools, adding subcommands, creating interactive TUI, styling terminal output, or implementing shell completions.
Cloud architecture design, migration, optimization, and disaster recovery across AWS and Azure. Use when designing VPCs/VNets, IAM/RBAC, compute/storage architectures, cost optimization, multi-cloud patterns, or planning migrations. Both Terraform and CLI approaches.
Datadog monitoring strategy, alert design, tagging governance, dashboard patterns, SLO strategy, log management, cost optimization, and cross-pillar correlation workflows. Use when making architectural decisions about what to monitor, how to alert, how to tag, or how to structure Datadog for a service or platform. Delegates execution to pup CLI and infrastructure-as-code to sre-engineer.
Kubernetes workload management, Helm chart development, cluster troubleshooting, custom operators, configuration management, and multi-cluster administration. Use when deploying workloads, writing Helm charts, debugging pods, creating operators, managing ConfigMaps/Secrets/RBAC, or working with multi-cluster setups.
| name | config-audit |
| description | Use when asked to audit configs, check config freshness, verify tool configs are up to date, or after upgrading nix flake inputs. |
Check every tool configured in common/ against its
installed version. Find deprecated keys, broken
references, and notable new options. Offer to fix
what's broken.
Audit against the INSTALLED version, not the latest
upstream release. Packages are pinned via nixpkgs —
the installed version may be significantly older than
the latest GitHub release. Run the version command
FIRST, then check config validity for THAT version.
Use tool --help, tool -c (default config dump),
or version-specific docs — not latest release notes.
Verify every claim before reporting:
tool -c or tool --help to confirm whether
a config key exists| Dir | Version cmd | Dump cmd | Repo |
|---|---|---|---|
ghostty | ghostty +version | ghostty +show-config --default | ghostty-org/ghostty |
lazygit | lazygit --version | lazygit -c | jesseduffield/lazygit |
k9s | k9s version | — | derailed/k9s |
herdr | herdr --version | — | ogulcancelik/herdr |
neovim | nvim --version | — | neovim/neovim |
gh-dash | gh extension list | — | dlvhdr/gh-dash |
pi | pi --version | — | earendil-works/pi |
zsh | oh-my-posh --version | — | JanDeDobbeleer/oh-my-posh |
git | git --version | — | — |
ssh | ssh -V | — | — |
programs | — | — | — |
If a common/ directory exists that isn't in this
table, audit it anyway — read the nix file, identify
the tool, and check its docs.
Dispatch one general-purpose agent per tool, ALL in
a single message for parallel execution.
Each agent prompt:
Read config files in
{repo_root}/common/{tool}/and check against the INSTALLED version.IMPORTANT: Run
{version_cmd}FIRST. All findings must be valid for the INSTALLED version, not latest upstream. Use{dump_cmd}if available to verify which keys the installed version recognizes. Usegh api repos/{repo}/releasesONLY for suggesting new options, never for claiming keys are removed.Find: (1) deprecated/removed keys, (2) invalid structure, (3) broken references, (4) redundant defaults, (5) notable new options.
Categorize: MUST_FIX (broken, verified against installed version), SHOULD_FIX (deprecated but working), CLEANUP (redundant), NEW_OPTION (available in latest upstream).
Report:
[CATEGORY] file:line — description. Concise, no preamble.
For neovim, also check plugin references and API
deprecations. For programs/, check Home Manager
module option validity.
Compile all agent results into one prioritized table:
| Priority | Tool | File | Issue |
|---|---|---|---|
| Must fix | ... | ... | ... |
| Should fix | ... | ... | ... |
| Cleanup | ... | ... | ... |
List new options separately. Then offer to apply must-fix and should-fix items.
Do NOT modify files during the audit — only after presenting findings and getting approval.