Commit
Skill Eipi-Tong/agentic-coding-starter-kit/.claude/skills/commit
A reusable agentic coding starter kit (Claude Code) for web projects
npx -y skills add Eipi-Tong/agentic-coding-starter-kit --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create a well-formed Conventional Commit. Use when the user says "commit", "commit my changes", or asks you to save progress.
SKILL.md
1.2 KB, as published. Nobody here has run it
Commit Skill
Step 1 — Check the working tree
git status
git diff --stat
If the tree is clean, tell the user and stop.
Step 2 — Check for violations
Before committing, verify:
- No
.envor secret files staged - No
console.log,TODO, orFIXMEin staged files - No build artifacts or
node_modulesstaged
If violations found, list them and stop. Do not commit.
Step 3 — Run quality checks
Run the project's lint and type-check commands (from BOOTSTRAP_FORM.md tooling section).
If they fail, stop and report.
Step 4 — Compose the message
Choose the correct type from .claude/rules/commit-rules.md.
Draft the commit message and show it to the user for confirmation before committing.
Format:
<type>(<scope>): <description>
[body if needed]
Step 5 — Commit
git add -p # stage interactively if multiple logical changes
git commit -m "<message>"
Step 6 — Confirm
Print the commit hash and subject line. Ask if the user wants to push.