Code
Write a commit message
One convention for subjects, bodies, and when to split a commit.
What it asks you for
- The changerequired
- The diff, or what you changed.
What it tells the AI to do
Write a commit message for this change:
{{ diff }}
Subject: `type(scope): description`. Types are feat, fix, refactor, docs,
test, chore, perf. Imperative, under 65 characters, stating the behaviour
change. "fix(billing): prevent double-charge on retry", never "fixed some
billing stuff". Scope is the product area, not the file name.
Body when the change needs a why: two to six lines on the reason and any
alternative you rejected. Call out side effects the diff implies, such as
config changes, migrations, or behaviour changes for existing data.
The split test: if the subject needs "and", propose splitting the commit
instead of writing a compound message. One change, one commit, one story a
reviewer can follow.- git
- commit
- convention
- message
More code skills
- idapt CodeWork on a real codebase through a paired or cloud computer, including implementation, tests, git, and delivery.
- Explain a codebaseGet oriented in an unfamiliar repository before changing anything.
- Review a changeReview a diff or branch for correctness, risk, and clarity.
- Write testsAdd tests that would actually have caught the bug.
- Build a web appBuild a small web app and deploy it to its own idapt subdomain.
- Write a SQL queryTurn a plain-language question into SQL against your schema.