om-check-and-commit

Runs configured validation gates, fixes failures, then commits and pushes the branch.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-check-and-commit-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-check-and-commit
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-check-and-commit
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-check-and-commit-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It removes the manual toil of verifying a branch before publication by running every configured CI-style validation command in order, fixing straightforward failures such as locale-file drift, and committing and pushing only when everything passes. ## Core Features & Use Cases - Configured validation gates: Reads the authoritative command list from .ai/agentic.config.json (validation.commands) and runs each gate in order, re-running failed checks after fixes until all pass. - Minimal in-scope fixes: Applies small, targeted fixes including locale key synchronization across all maintained locales, without reverting unrelated user changes. - Safe publication: Commits with a conventional-commit subject and pushes the current branch only when the user explicitly asked for publication, never skipping hooks, amending, or force-pushing. - Use Case: Before opening a pull request, ask the agent to check the branch; it runs lint, typecheck, and tests from the repo config, fixes a missing locale key, re-runs the gates, and pushes a clean commit. ## Quick Start Ask the agent to check the current branch against the configured validation gates, fix any failures, and then commit and push it.

Frequently Asked Questions about om-check-and-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a git branch before committing and pushing?

Run every validation command configured in .ai/agentic.config.json in order, fix any failures, and re-run failed gates until all pass. Only then commit with a conventional-commit message and push the current branch.

How are the validation commands for the branch check configured?

The commands come from the validation.commands array in .ai/agentic.config.json, read with jq. The configured list is authoritative, so commands are never skipped or substituted with alternatives.

Does it commit and push automatically after checks pass?

No. It commits and pushes only when the user explicitly asks for publication in the same request. Otherwise it stops after reporting the verification result, and it never force-pushes, amends commits, or skips commit hooks.

How does it handle locale file drift during validation?

When the repo has a locale sync or usage check among its gates, drift is treated as a required failure to fix. Missing keys are added across every maintained locale, unused keys introduced by the current work are removed, and unrelated drift is reported as a blocker.

What happens if a validation gate keeps failing after fixes?

The run stops without committing and reports the exact blocker: the failing command, the first error, and what a human needs to decide. Success is never claimed while any required gate is still failing.