cli-code-skills
CLAUDE.md5 starsChanged 8 months agoMITView on GitHub
Skills are installed as copies in ~/.claude/skills/ for Claude Code, ~/.codex/skills/ for Codex, and ~/.jcode/skills/ for Jcode (global, available in all projects). Jcode is only touched when ~/.jcode exists. Source of truth is this repo (~/workspace/cli-code-skills/). After modifying a skill in this repo, copy it to every runtime: Or install only one runtime: The installer removes each destination skill before copying it. That avoids stale files when a reference is renamed or deleted. The safe direction is repo → runtime.…
In this repository40 other files it gives its agents.
- .cursor/rules/cli-audit-code.mdcCursor rule
- .cursor/rules/cli-audit-doc.mdcCursor rule
- .cursor/rules/cli-forge-arch.mdcCursor rule
- .cursor/rules/cli-forge-schema.mdcCursor rule
- cli-audit-codeSkill
- cli-audit-dataSkill
- cli-audit-docSkill
- cli-audit-driftSkill
- cli-audit-hanoiSkill
- cli-audit-reviewSkill
- cli-audit-shellSkill
- cli-audit-syncSkill
- cli-audit-tangleSkill
- cli-audit-testSkill
- cli-audit-wizardSkill
- cli-audit-xraySkill
- cli-cycleSkill
- cli-forge-archSkill
- cli-forge-chefSkill
- cli-forge-choice-uxSkill
- cli-forge-dataSkill
- cli-forge-demoSkill
- cli-forge-docSkill
- cli-forge-githubSkill
- cli-forge-hldSkill
- cli-forge-infraSkill
- cli-forge-lldSkill
- cli-forge-oci-rootlessSkill
- cli-forge-perfSkill
- cli-forge-pipelineSkill
- cli-forge-plumeSkill
- cli-forge-prezSkill
- cli-forge-profileSkill
- cli-forge-quorumSkill
- cli-forge-readmeSkill
- cli-forge-resilienceSkill
- cli-forge-schemaSkill
- cli-forge-treeSkill
- cli-git-conventionalSkill
- cli-watermarkSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
If you (or a session) edited a skill directly in ~/.claude/skills/, run --pull-claude to bring it back into the repo, review git diff, …
- Distinctive: line 46
Do NOT use symlinks — use real copies.
- Distinctive: line 50
Before committing or installing changes, run:
- Very specific: line 93
Use clement <cliard@a00.fr> for this repo.
- Distinctive: line 98
Follow Conventional Commits v1.0.0 spec.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md — cli-code-skills
Skills installation
Skills are installed as copies in ~/.claude/skills/ for Claude Code,
~/.codex/skills/ for Codex, and ~/.jcode/skills/ for Jcode (global,
available in all projects). Jcode is only touched when ~/.jcode exists.
Source of truth is this repo (~/workspace/cli-code-skills/).
After modifying a skill in this repo, copy it to every runtime:
scripts/install_skills.shOr install only one runtime:
scripts/install_skills.sh --claude
scripts/install_skills.sh --codex
scripts/install_skills.sh --jcodeThe installer removes each destination skill before copying it. That avoids stale files when a reference is renamed or deleted.
The safe direction is repo → runtime. If a runtime copy was edited in place and
that edit is not yet in the repo, the installer refuses to overwrite it
(exit 3) rather than destroy it. It tracks this with a .skills-manifest written
into each runtime skills root at install time.
scripts/install_skills.sh --check # report divergence, change nothing
scripts/install_skills.sh --pull-claude # copy Claude in-place edits back into the repo
scripts/install_skills.sh --pull-codex # copy Codex in-place edits back into the repo
scripts/install_skills.sh --pull-jcode # copy Jcode in-place edits back into the repo
scripts/install_skills.sh --force # overwrite even runtime-ahead editsIf you (or a session) edited a skill directly in ~/.claude/skills/, run
--pull-claude to bring it back into the repo, review git diff, validate, and
commit — then a normal install re-syncs both runtimes.
Shared files (gotchas.md and shared/) are referenced by root SKILL.md
files as ../<name> and by references/ files as ../../<name>.
The installer copies them to the skills root for every runtime.
Do NOT use symlinks — use real copies.
Validation
Before committing or installing changes, run:
python3 scripts/validate_skills.pyThe validator checks frontmatter, skill counts, README/CLAUDE inventories,
shared-file paths, and Claude/Codex-neutral cli-cycle orchestration.
It also enforces the Agent Skills spec limits: name <= 64 chars and
lowercase/digits/hyphens only, description <= 1024 chars (over the limit the
skill is rejected by the API). SKILL.md bodies over 500 lines are reported as
WARN, following Anthropic's progressive-disclosure guidance: move detail into
references/ so the body stays cheap to load.
Evaluations
evals/ holds one JSON case per scenario plus the deliberately flawed fixtures
they point at. There is no scored runner: grading a skill run needs a model in
the loop. What is automated keeps the cases honest.
python3 scripts/check_evals.pyIt rejects a case whose skill or fixture does not exist, or that cites a
dimension ID the skill never defines. See evals/README.md. Fixtures are
broken on purpose and must not be repaired.
Current skills (36)
Audit (12): cli-audit-code, cli-audit-data, cli-audit-doc, cli-audit-drift, cli-audit-hanoi, cli-audit-review, cli-audit-shell, cli-audit-sync, cli-audit-tangle, cli-audit-test, cli-audit-wizard, cli-audit-xray
Cycle (1): cli-cycle
Forge (21): cli-forge-arch, cli-forge-chef, cli-forge-choice-ux, cli-forge-data, cli-forge-demo, cli-forge-doc, cli-forge-github, cli-forge-hld, cli-forge-infra, cli-forge-lld, cli-forge-oci-rootless, cli-forge-perf, cli-forge-pipeline, cli-forge-plume, cli-forge-prez, cli-forge-profile, cli-forge-quorum, cli-forge-readme, cli-forge-resilience, cli-forge-schema, cli-forge-tree
Git (1): cli-git-conventional
Watermark (1): cli-watermark
Git identity
Use clement <cliard@a00.fr> for this repo. Never use naval-group email.
Commit style
This repo uses the cli-git-conventional skill. Never add Co-Authored-By trailers.
Follow Conventional Commits v1.0.0 spec. Ghostwriter style — human voice, no AI markers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

