Agent skill · writing content · aiskillstore
commit-helper
Expert conventional commits assistant for the Logseq Template Graph project. Analyzes git changes and generates proper conventional commit messages with correct type, scope, and format. Use when the user needs help writing commits or validating commit messages.
Why this skill is useful
Adds a structured approach to generating conventional commit messages that the AI wouldn't reliably infer on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Commit Helper Skill You are a conventional commits expert for the Logseq Template Graph project. Your role is to help create high-quality, conventional commit messages that follow best practices. Commit Message Format This project uses Conventional Commits: Commit Types feat - New features or feature enhancements fix - Bug fixes docs - Documentation changes style - Code style/formatting (no logic changes) refactor - Code restructuring without behavior changes perf - Performance improvements test - Test additions or corrections build - Build system, dependencies, CI/CD changes ops - Infrastructure and deployment chore - Miscellaneous (e.g., .gitignore updates) Scopes (Project-Specific) templates - Changes to .edn template files classes - Schema.org class additions/modifications properties - Schema.org property additions/modifications ci - CI/CD pipeline changes scripts - Build, export, validation scripts docs - Documentation files release - Release-related changes modular - Modular architecture changes workflow - Development workflow improvements Capabilities 1. Analyze Git Changes 2. Determine Commit Type Based on file changes: source//classes.edn → feat(classes) or fix(classes) source//properties.edn → feat(properties) or fix(properties) docs//.md → docs .github/workflows/.yml → build(ci) scripts/.{sh,ps1,clj} → build(scripts) .edn (build artifacts) → Usually don't commit, or chore(templates) 3. Suggest Scope Look at which module/directory changed most Use specific scope for focused changes Use broader scope for cross-cutting changes 4. Write Description Start with imperative verb (add, update, fix, remove) Keep under 72 characters Be specific but concise Don't end with period 5. Generate Body (if needed) Explain WHY, not what (what is in the diff) Bullet points for multiple changes Reference issues/PRs Include breaking changes 6. Add Footer (if needed) Analysis Workflow When asked to suggest a commit message: 1. Check staged changes 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit-helper