Commit All
--- name: "commit-all" title: "Commit All Changes" description: "Commit all changes to git using conventional commit format" arguments: - name: "instructions" description: "Additional instructions about the commit message (e.g. feat, #12, Co-authored-by: name). Default: no additional instructions" default: "" examples: - "@commit" # commit with auto generated commit message - "@commit feat" # specify commit type - "@commit feat(web)" # specify commit type and scope - "@commit 'feat(web) #12'" # specify related resources --- Commit changes to git using conventional commit format. You should use `git status --porcelain` to see all changes including untracked files, use `git diff HEAD` to see tracked change contents, and read untracked file contents to understand the changes. MUST NOT create new git repositories. Abort if no git repository exists. Never use `--no-verify` flag unless user explicitly asks for it. Additional instructions that should be included in the commit message: {instructions}
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{instructions}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo DiscreteTom/prompts (no explicit license). A "Commit All" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
DiscreteTom/prompts · no explicit license
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions