Full Byte Developer.

Turn a repeated prompt into a Claude Code skill

Create a small skill, choose its scope and verify it against a known file change.

Originally posted · Published here · 1 source

Claude Code's skills guide includes a change-summary skill that loads the current Git diff before responding. A skill directory holds a SKILL.md file with metadata and instructions. [1]

Choose where it belongs

The documented personal directory is ~/.claude/skills/summarize-changes/. A project skill goes under .claude/skills/ instead, where it can be committed for the team. [1]

Create SKILL.md using the example in the linked guide. Its description tells Claude when to use the skill. The example's dynamic command reads git diff HEAD into the prompt. [1]

Check it on a known change

Make one small edit in a test repository. Invoke /summarize-changes and compare the summary with the actual diff. The documented command reads tracked changes relative to HEAD; check untracked files separately.

For a skill you want to invoke only yourself, the documentation provides disable-model-invocation: true. [1] That controls automatic invocation, not the permissions of commands inside the skill. Read those commands before enabling a skill from another source.

Keep this guide

By Full Byte Developer

Original post: Instagram post

Filed under Claude Code

Sources

Next in this stack