Generates conventional commit messages with logical grouping for RTS development workflows.
npx skills add https://github.com/Ohmnia/site-build --skill git-commit-ohmnia
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/Ohmnia/site-build/tree/main/.opencode/skills/git-commit Command: npx skills add https://github.com/Ohmnia/site-build --skill git-commit-ohmnia
type(scope): summary format with allowed types like feat, fix, perf, refactor, docs, config, test, chore, and investigate. - RTS-Specific Scopes: Provides preferred scopes for game development such as movement, pathfinding, ecs, rendering, combat, and selection. - Commit Hygiene Rules: Separates refactors from features, splits unrelated changes, and rejects vague messages like "fix stuff" or "wip". - Use Case: After an AI coding session modifies pathfinding, rendering, and docs together, use this Skill to split the work into three focused commits with proper scopes and summaries. ## Quick Start Ask the AI to review the staged changes and generate conventional commit messages grouped by logical purpose.High-intent search queries and answers about installing and using this skill.
Use the format type(scope): concise summary, where type is one of feat, fix, perf, refactor, docs, config, test, chore, or investigate. For example, feat(movement): add formation slot assignment clearly states the change type, affected system, and purpose.
Identify logical change groups first, then separate unrelated changes such as gameplay, rendering, refactors, and formatting into individual commits. Each commit should be small, focused, reviewable, and reversible with a single clear purpose.
Use scopes matching the affected system, such as simulation, movement, steering, pathfinding, ecs, rendering, selection, camera, combat, economy, ui, agents, tooling, performance, or terrain. Consistent scopes make the git history searchable by subsystem.
Mixing refactors with features makes reviews harder and hides behavioral changes inside structural edits. A refactor commit must not imply gameplay changes, so refactor(ecs): flatten unit transform storage is correct while bundling it with a new feature is not.
Vague messages like fix stuff, misc changes, wip, updates, cleanup, or more work are anti-patterns because they communicate nothing about intent or impact. Performance commits should also explain what bottleneck changed and what scale issue was addressed.
AnthonyPoschenCreate small, reviewable Git commits with descriptive messages and AI assistance trailers.
wendeus0Finalize Git feature branches by cleaning commits and preparing pull requests.
GelioVerify each commit on the current branch passes the project's full check suite.
tjmgregorySquash merge GitHub pull requests via gh CLI with conventional commit messages.