Claude Code slash commands

Create well-formatted git commits — conventional-commit type + emoji, split into atomic commits when a diff covers more than one concern.

Try it for: Make this your default way to commit, full stop — once it's in .claude/commands/, every commit on the project gets the same consistent style with zero extra thought from you.

Branch, commit (split into logical units automatically), push, and open a pull request in one command.

Try it for: Pair it with /commit as your end-of-task ritual: /commit to wrap up, then /create-pr to hand it off for review — "done coding" to "PR open" in two commands instead of a dozen.

Look at what actually changed on this branch and rename it to something descriptive — no more guessing a name before you've written the code.

Try it for: Stop overthinking branch names at the start of a task entirely — just branch as "wip" and run this at the end. It removes a tiny but constant naming-things tax from your day.

Give it an issue number — it reads the issue via `gh`, finds the relevant code, fixes it, tests it, and commits.

Try it for: Work through a whole backlog of small, well-described bugs this way — one `/fix-github-issue 142`, `/fix-github-issue 143`... per issue — and clear a sprint's worth of minor tickets in an afternoon instead of a week.

Add a properly formatted entry to CHANGELOG.md — Keep a Changelog style, correct section, no manual formatting.

Try it for: Make it part of your release habit, not just an afterthought: run it the moment you decide something's "done", so the changelog is always current instead of reconstructed from git log at release time.

A full project todo manager — add, complete, remove, due dates, sorting — living in a plain todos.md file.

Try it for: Use it as your whole project tracker for solo or small side-projects — skip signing up for Trello/Linear/Asana entirely and keep the task list versioned in the same repo as the code it's about.