Proposes grouped git commits with conventional messages and waits for user confirmation.
npx skills add https://github.com/ledtorch/coding-agent-workflow --skill commit-ledtorch
Please help me install this Agent Skill. Skill: commit Source: https://github.com/ledtorch/coding-agent-workflow/tree/main/skills/commit Command: npx skills add https://github.com/ledtorch/coding-agent-workflow --skill commit-ledtorch
High-intent search queries and answers about installing and using this skill.
Use the format type(scope): description, where type is feat, fix, refact, docs, chore, or similar. Keep the description under 72 characters in imperative present tense, and match the existing style shown by git log.
Group changes by topic so each commit contains one logical change. Stage only the files belonging to one topic at a time, then create separate commits sequentially with their own type and scope prefixes.
Yes. When changes are staged, the staged diff defines the commit scope and unrelated unstaged files are excluded. It only flags directly related forgotten files and asks whether to include them.
No. Every proposal waits for an explicit Y or N response before creating commits. It also never uses --no-verify, --force, or amend unless you explicitly request it.
The workflow refuses to commit files that may contain secrets such as .env files, credentials, or private keys, and warns you instead so you can exclude them before committing.
oporpinoGuides structured dialogue to write and approve technical specification documents.
e-xodePrepare a GitHub release for the vue-ssr starter kit with version bumps and changelog updates.
SamyakJhaveriScan recent code changes for duplicated logic, dead code, and magic numbers.
luanPerform hunk-level Git operations including staging, unstaging, discarding, and commit splitting.
