Menu
Generate conventional commit message from staged or unstaged changes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Checks projects and packages for CVEs using Socket.dev CLI and native audit commands. Use when installing or auditing dependencies for vulnerabilities, evaluating a package before install, or scanning a project's dependency tree.
Audit the current project's memory store (`~/.claude/projects/<encoded-cwd>/memory/`) and prune memories that no longer match the project state — dead file/function/flag references, past-dated project memories, orphaned index entries, and duplicates. Suggests candidates with rationale and requires per-item confirmation before deleting; does not edit memory bodies. Use when the user says "prune memory", "clean up memory", "audit memory", "memory is stale", "remove old memories", or invokes /prune-memory.
Symlink every skill in this repo into one or more agent skills directories (defaults to ~/.claude/skills/ and ~/.agents/skills/) so the skills become globally discoverable. Use when the user says "install these skills", "make these skills global", "symlink skills to ~/.claude", "symlink skills to ~/.agents", "register the skills", or wants to update the global skill set after editing skills here.
Build, validate, and exercise the agent-skills registry. Use when asked to run agent-skills, install its deps, lint or test it, run its bats suites, exercise a Claude Code hook, regenerate the index files, or symlink the skills out to ~/.claude / ~/.agents / ~/.cursor / ~/.opencode.
Concise, technically-precise response style with kawaii flourishes (emojis, emoticons, otaku suffixes). Use when the user wants playful agent output while keeping technical accuracy and brevity.
Generates a changelog by analyzing git history and tags. Use when the user asks to generate, write, or update a changelog.
| name | gcm |
| description | Generate conventional commit message from staged or unstaged changes |
| model | inherit |
| allowed-tools | ["Bash(git)"] |
| user-invocable | true |
Generate a conventional commit message for the current changes.
git log --oneline -10 and match the existing commit style.git diff --cached to read staged changes. If empty, run git diff for unstaged changes.<type>(<scope>): <description>
<body>
fix, feat, docs, style, refactor, test, chore, spelling, rename
Infer from changed file paths. If changes span multiple scopes, use the most significant one or omit the scope.
Include a body when the change is non-trivial. Explain why, not what. Separate from title with a blank line. Wrap at 72 characters.
If the change is breaking, add ! after the scope and a BREAKING CHANGE: footer:
feat(sdk)!: rename updateSnapshot to updateProject
BREAKING CHANGE: updateSnapshot removed, use updateProject(projectId, { snapshotId }) instead.
$@