Commit
DevelopmentcommitCommit is an Agent Skill for development published in the windmill-labs/windmill repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/windmill-labs/windmill/blob/HEAD/.agents/skills/commit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/commit, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Git Commit Skill
Create a focused, single-line commit following conventional commit conventions.
Instructions
- Analyze changes: Run
git statusandgit diffto understand what was modified - Stage only modified files: Add files individually by name. NEVER use
git add -Aorgit add . - Write commit message: Follow the conventional commit format as a single line
Conventional Commit Format
<type>: <description>
Types
feat: New feature or capabilityfix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featuredocs: Documentation only changesstyle: Formatting, missing semicolons, etc (no code change)test: Adding or correcting testschore: Maintenance tasks, dependency updates, etcperf: Performance improvement
Rules
- Message MUST be a single line (no multi-line messages)
- Description should be lowercase, imperative mood ("add" not "added")
- No period at the end
- Keep under 72 characters total
Examples
feat: add token usage tracking for AI providers
fix: resolve null pointer in job executor
refactor: extract common validation logic
docs: update API endpoint documentation
chore: upgrade sqlx to 0.7
Execution Steps
- Run
git statusto see all changes - Run
git diffto understand the changes in detail - Run
git log --oneline -5to see recent commit style - Stage ONLY the modified/relevant files:
git add <file1> <file2> ... - Create the commit with conventional format:
git commit -m "<type>: <description>" - Run
git statusto verify the commit succeeded