cap

Stage all changes, craft a commit message, and push the current branch.

30|2|Updated Apr 28, 2026

Search Tags:#automation #git #workflow #commit #conventions #push #version-control

Ready to run

npx skills add https://github.com/hawkyre/hawk-skills --skill cap-hawkyre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cap
Source: https://github.com/hawkyre/hawk-skills/tree/main/skills/cap
Command: npx skills add https://github.com/hawkyre/hawk-skills --skill cap-hawkyre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe and efficient staging, message drafting, and pushing of code changes to speed up turnaround without manual git overhead.

Core Features & Use Cases

Stage all changes in the working tree and inspect diffs to craft a commit that matches the repository's style.
Draft a concise, purpose-driven commit message and push to the current branch, with safeguards against secrets or unintended pushes.
Use case: when you want to ship a small set of changes quickly while preserving the project’s commit conventions.

Quick Start

Stage all changes, craft a concise commit message in the repo's style, and push the current branch.

Frequently Asked Questions about cap

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

FAQPage Schema

How do I stage, commit, and push git changes in one step?▼

To stage, commit, and push git changes in one step, you can automate the workflow by analyzing the working tree diff and recent commits to generate a convention-matching commit message, then safely push the current branch.

Can I automatically generate a commit message that matches my repository's conventions?▼

Yes, you can automatically generate a commit message matching your repository conventions by analyzing recent commit history and diff stats to draft a concise, purpose-driven message that aligns with the project's existing style.

Does automating a git commit and push risk exposing secrets or forcing branch overwrites?▼

Automating a git commit and push does not risk exposing secrets or forcing overwrites when safeguards are in place to block dangerous actions like force pushes and secret exposure, ensuring only safe staging and pushing occurs.

What is the best way to speed up git workflow turnaround for small changes?▼

The best way to speed up git workflow turnaround for small changes is to automate the manual overhead of staging, message drafting, and pushing, allowing you to ship code quickly while preserving commit conventions.

How does automated commit messaging determine the appropriate git push behavior?▼

Automated commit messaging determines appropriate git push behavior by analyzing the repository's git status, diff statistics, and recent commit history to ensure the push aligns with established project conventions and current branch targets.

Do I need to manually stage files before automating a git commit and push?▼

No, you do not need to manually stage files before automating a git commit and push, as the process requires explicit staging of all working tree changes internally before crafting the commit message and pushing.