diet103/claude-code-infrastructure-showcase

source-command-verify-setup

Run the infrastructure health check and fix anything that fails

First seen Aug 3, 2026

Installation

$ npx skills add diet103/claude-code-infrastructure-showcase --skill source-command-verify-setup

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from diet103/claude-code-infrastructure-showcase.

npx skills add diet103/claude-code-infrastructure-showcase

Browse all from diet103/claude-code-infrastructure-showcase

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 10.0K
License LICENSE
Default branch main
Open issues 14
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,449 B
  • docs SUMMARY.md 98 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

source-command-verify-setup

Use this skill when the user asks to run the migrated source command verify-setup.

Command Template

Run the Codex infrastructure health check and get it fully green.

Steps

  1. Run the health check from the project root:

``bash bash .Codex/scripts/verify-setup.sh ``

  1. For every [FAIL] line, apply the printed fix. Common fixes:

- Dependencies missing: cd .Codex/hooks && npm install - Scripts not executable: chmod +x .Codex/hooks/*.sh - Invalid JSON in .Codex/settings.json or .Codex/skills/skill-rules.json: read the file, find the syntax error (usually a trailing comma), and repair it without changing any settings values - Missing hook scripts registered in settings.json: ask the user whether to copy them from the showcase repo (https://github.com/diet103/Codex-infrastructure-showcase) or remove the dead registrations

  1. Re-run the script after each fix until it reports 0 failed.
  1. [WARN] lines are optional features (session intelligence, jq-based file tracking, AI classification keys). Do NOT install API keys or system packages on the user's behalf - summarize what each warning means and let the user decide.
  1. Report the final result to the user: what was broken, what you fixed, and what (if anything) remains as a warning.