Create conventional commits from staged changes with GitHub issue references.
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill commit-ryan-mahoney
Please help me install this Agent Skill. Skill: commit Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/commit Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill commit-ryan-mahoney
This Skill automates turning staged changes into a clean, conventional commit message that references the relevant GitHub issue when available, reducing manual guesswork and improving history clarity.
Provide an issue number or rely on the branch naming, then trigger the commit operation to generate and apply a conventional commit for the staged changes.
High-intent search queries and answers about installing and using this skill.
You can generate a conventional commit automatically by providing a GitHub issue number or relying on branch naming. The Skill reads the issue context, analyzes staged diffs, and commits the changes with a standardized message referencing the issue.
Issue context works by extracting the issue number from your current branch name or provided input. The Skill reads this context, analyzes the staged changes, and embeds the issue reference directly into the generated conventional commit message.
Yes, you need to manually stage files before using this conventional commit automation tool. The Skill reviews the already staged diffs to compose the commit message, rather than staging the changes itself.
Yes, you can use branch naming to reference a GitHub issue in your version-control commits. The Skill identifies the issue number from the branch name, analyzes staged changes, and commits with a conventional message that includes the reference.
The best way to standardize git history with conventional commits is to automate message generation from staged diffs and issue context. This Skill analyzes changes, applies a conventional format, and references the relevant issue number.
cattboyStage changes and commit with conventional messages enriched by GitHub context.
AndrewDrygaCreate semantic version tags from changelogs and push them to Git.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.
itsjaviGenerate Conventional Commit messages from staged Git changes.
