Anything you have pasted more than twice — a review checklist, a release procedure, a bug-report format — is a skill waiting to be written.
A folder under
.claude/skills/ with a SKILL.md. The description tells Claude when to use it;
$ARGUMENTS takes what you typed;
!`…` injects command output.
Run
/skills. Your skill should be listed and invocable as
/security-review.
A markdown file under
.claude/agents/ with a description and a restricted
tools: list. Claude delegates to it, or you invoke it with
@.
Hooks are deterministic — they run every time, not when Claude remembers. Formatting after every edit is the best first hook.
Run
/hooks. Hooks load at session start, so restart the session after editing settings.
