Ase meta commit
Agentic Software Engineering (ASE)
npx -y skills add rse/ase --skill ase-meta-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Determine commit message for staged Git changes.
SKILL.md
2.4 KB, as published. Nobody here has run it
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
<skill name="ase-meta-commit"> Git Commit </skill> <expand name="getopt" arg1="ase-meta-commit"> $ARGUMENTS </expand> <objective> Help to *craft* a *concise commit message* for the currently staged Git changes. </objective> <flow>-
<step id="STEP 1: Find out staged changes">
Run the following command to find out details of what changes are currently staged in the Git index for commit:
</step>git diff --cached -
<step id="STEP 2: Craft a consolidated commit message">
Craft a commit <message/> in the following format:
<type/>: <summary/>The known <type/>s (kept deliberately in sync with the intent groups of the
ase-meta-diffandase-meta-changelogskills) and their usual corresponding kind of change are:FEATURE: new functionality or configurationIMPROVEMENT: improved functionality or configurationBUGFIX: corrected functionality or configurationUPDATE: updated functionality or configurationCLEANUP: cleaned up functionality or configurationREFACTOR: refactored functionality or configuration
The rules for generating <summary/> are:
- Use a maximum of 60-80 characters
- Use imperative mood ("add" not "added")
- Use no period at the end
- Use no Markdown formatting
Output this crafted commit message with the following <template/>:
<template> Commit Message: **<message/>** </template>Do not output any further explanation.
Finally, give the closing hint by expanding the following (which, depending on the configured <ase-guidance-level/>, may expand into nothing and hence emit no output at all):
<if condition=" a `CHANGELOG.md` file exists in the project (or in any affected sub-package) and is *not* itself part of the staged changes "> <ase-tpl-hint level="normal"> The staged changes do not touch
</step>CHANGELOG.md-- use/ase-meta-changelogto update its entries before committing. </ase-tpl-hint> </if>