Use this skill to review pending changes, select only the relevant files for staging, and create a focused Git commit. It formats the single-line message with a Conventional Commits type such as feat, fix, or docs, and checks the resulting status.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Create a focused, single-line commit following conventional commit conventions.
git status and git diff to understand what was modifiedgit add -A or git add .<type>: <description>
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 improvementfeat: 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
git status to see all changesgit diff to understand the changes in detailgit log --oneline -5 to see recent commit stylegit add <file1> <file2> ...git commit -m "<type>: <description>"
git status to verify the commit succeededNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan the code changes needed to add a TriggerCrud-based trigger to Windmill. The checklist covers backend, database, API, CLI, frontend, capture, and validation work so the new trigger can be managed across the product.
Improve Windmill’s AI chat by reviewing its tools, prompts, result shapes, and context usage. The guidance helps place shared instructions where chat and CLI can use them, reduce repeated token costs, and compare behavior before and after changes with A/B evaluations.
Create and run black-box benchmarks for Windmill AI generation modes such as flows, apps, scripts, CLI, and global requests. Each case exercises the production path, checks hard requirements, and uses an LLM judge to assess user-facing behavior before and after changes.
Use this reference to work with Windmill resources from the command line, including scripts, flows, datatables, and workspace settings. It also covers listing jobs, inspecting details and logs, retrieving results, and rerunning or restarting executions when investigating failures.
Use this skill to shape modules with small interfaces and substantial behavior behind them. It helps you decide where a seam belongs, reduce complexity exposed to callers, and make code easier to test and maintain.
Manage schema changes to Windmill data tables through versioned SQL migrations, including applying and rolling them back. The guide also explains role-based access, migration safety, and how changes affect workspaces, apps, and scripts.