publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests
Use when about to refactor or refine an existing skill, its SKILL.md or sibling files, from a full restructure down to a one-line wording fix; a change that looks too small to need this skill is not an exemption. Not for creating a skill from scratch
$ npx -y skills add vinta/hal-9000 --skill refactor-skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/refactor-skillContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when about to refactor or refine an existing skill, its SKILL.md or sibling files, from a full restructure down to a one-line wording fix; a change that looks too small to need this skill is not an exemption. Not for creating a skill from scratch
name: refactor-skill description: Use when about to refactor or refine an existing skill, its SKILL.md or sibling files, from a full restructure down to a one-line wording fix; a change that looks too small to need this skill is not an exemption. Not for creating a skill from scratch argument-hint: [skill name | path/to/SKILL.md] allowed-tools: - WebFetch(domain:platform.claude.com) - WebFetch(domain:code.claude.com) - WebFetch(domain:developers.openai.com) - Edit(**/skills/**)
Refactor a skill. A skill spends two budgets. Its description is loaded into every session, so each word there must do triggering work. Its body enters the context on invocation and stays there for the rest of the session, so each line there must guide every path through the skill. Conditional material moves behind a pointer; unnecessary material leaves the skill.
Use `AskUserQuestion` in Claude Code or `request_user_input` in Codex when available.
1. **Pick the target.** If the invocation names one, resolve it to its `SKILL.md`. Otherwise ask which skill. For a full audit, read `SKILL.md` and every sibling file in its directory. For a targeted change, read `SKILL.md`, affected files, and references needed to assess their interactions. That change sets the scope: the verdicts below cover the lines it adds or touches, the rest of the skill stays as it is, and anything noticed there is a follow-up.
2. **Fetch the guides.** The platform and model guides below calibrate the delete, demote, and rewrite verdicts.
3. **Audit.** Give every frontmatter key, body instruction, and sibling file in scope exactly one verdict, judged against its bar below. Done when nothing in scope lacks a verdict.
The bar per part:
4. **Get decisions.** Reuse changes and verdicts the user already authorized. Resolve contradictions from instruction priority and explicit user intent where possible; for each unresolved one, ask with `AskUserQuestion` or `request_user_input`, each conflicting version an option. Present any remaining delete and demote proposals and collect sign-off. Preserve explicit review boundaries and leave unapproved proposals untouched.
5. **Rewrite.** Apply the authorized changes and verdicts in one pass, without asking again. Apply only those: anything else noticed while editing is a fol
Opinionated AI coding agent and dev environment automation for macOS that dominates your dev setup like cats rule the Internet. This project is named after Arthur C.
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests
(project) Use when upgrading install tasks in playbooks/roles/ against upstream docs — bumping a pinned version, adopting a newly…
Use when auditing Claude Code or Codex settings and env vars against the latest docs to suggest tailored changes
Use when about to choose, configure, or refine a tool, library, config format, API pattern, or project setup, or before proposing…
Use when the user asks for a blindspot pass or to find their unknown unknowns, or signals unfamiliarity with a domain, tool, or…
Use when making any git commit. Pass the failure, false claim, or risk the changes fix as the argument; for an addition or a…