Stats
Actions
Tags
From claude-leverage
Bootstraps conventions.yml at repo root with inferred casing rules, denylist, and directory roles. Idempotent; never overwrites populated files. Run after init-repo.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-leverage:conventions-init [--noninteractive][--noninteractive]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bootstraps `conventions.yml` at the repo root — the profile the `context-surface`
Bootstraps conventions.yml at the repo root — the profile the context-surface
hook surfaces to an agent before it edits a source file (casing rules, a
vague-name denylist, directory roles, and divergent house rules the model cannot
infer). Block-style YAML only, so the stdlib fallback parser stays reliable.
It infers the mechanical parts (casing, structure) and asks the user for the house rules — it never invents a convention the repo does not actually hold.
/init-repo.conventions.yml
yet means the whole steering loop is a no-op).Do NOT invoke for: per-function docs (those are docstrings), or to auto-write house rules the team has not agreed on.
git rev-parse --show-toplevel); if not a repo, STOP
and suggest git init / /init-repo.conventions.yml is absent, bootstrap. If it exists, do
NOT rewrite it (stdlib YAML loses the human-written consistency comments);
instead print the suggested draft below and tell the user to merge by hand.python scripts/score_adherence.py --repo . if the
plugin's scorer is available, and read metrics.casing_consistency.by_kind[*] .dominant for functions / types / constants. Python-first: if there are
no .py files (or the scorer is absent), leave casing values blank with a
comment for the user — never guess from an unsupported language.src/,
lib/, app/, scripts/, tests/, …) that exist; write each as a root key
with a blank role string for the user to fill.data, result, tmp,
handle, process); the user can extend.consistency as a commented template — house rules are the user's
to write (same "never invent" rule as glossary-init).conventions.yml (bootstrap mode) with the schema_version "1.x"
comment, block-style. In existing-file mode, print the draft instead./refresh-context-map so the manifest (and thus the
hook) picks up the new conventions, and offer a one-line AGENTS.md pointer.consistency block is the user's; the skill
only scaffolds it.conventions.yml. Existing-file mode prints
suggestions for manual merge (preserves the user's comments).--noninteractive — write the inferred skeleton with blank roles and a
commented consistency block, no prompts./refresh-context-map.score_adherence.py / /repo-doctor.Same SKILL.md ships in Codex via scripts/install-codex.sh. No tool-specific
divergence.
npx claudepluginhub filip-podstavec/claude-leverage --plugin claude-leverageGenerates project-specific CLAUDE.md rules by detecting stack from package.json, Cargo.toml, pyproject.toml, go.mod, git log, and user-selecting categories like response format, library preference, code review stance. Use for new projects, repo onboarding, or establishing conventions.
Records coding conventions in CONVENTIONS.md to standardize repeated patterns like naming, formatting, or structure after 2-3 uses.
Bootstraps a repository with claude-leverage stack conventions: AGENTS.md, CLAUDE.md, .gitignore patterns, and optional language-specific logging templates. Interactive and idempotent.