commit-push
Commit scoped changes, push a branch, open or update a PR, and keep driving profile-defined CI, passive review, merge, and post-merge loops until success or a hard blocker remains.
Best use case
commit-push is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Commit scoped changes, push a branch, open or update a PR, and keep driving profile-defined CI, passive review, merge, and post-merge loops until success or a hard blocker remains.
Teams using commit-push should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit-push/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit-push Compares
| Feature / Agent | commit-push | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Commit scoped changes, push a branch, open or update a PR, and keep driving profile-defined CI, passive review, merge, and post-merge loops until success or a hard blocker remains.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit Push This is a local discovery wrapper for the shared Factory skill at `factory/skills/commit-push/SKILL.md`. Before using this skill: 1. Verify `factory/skills/commit-push/SKILL.md` exists. 2. If it is missing, stop and ask the user to run: ```bash git submodule update --init factory ``` Then read `factory/skills/commit-push/SKILL.md` and follow that Factory skill exactly, using the active `gait` repo profile unless the user provides another explicit profile. Do not treat this wrapper as the source of truth. The Factory skill is authoritative. Gait repository skill contract: - When command evidence is needed, prefer `gait doctor --json` or another active-profile `gait ... --json` command from `factory/profiles/gait.yaml`. - Require `--json` output for machine-readable command evidence.