generic-automation-and-it/smooth-ai-stockanalysis / .agents/skills/git-commit-push
git-commit-push
VerifiedCommit current changes with conventional commits format and push to remote repository. Use when committing and pushing changes to the upstream remote.
| File | Kind | Size |
|---|---|---|
| AGENTS.md | markdown | 1.1 KB |
| SKILL.md | skill md | 3.6 KB |
| agents/openai.yaml | config | 301 B |
| scripts/push.shexecutable | script | 987 B |
AGENTS.md
View on GitHub# git-commit-push — AGENTS.md
## TL;DR
Middle of the git skill chain: delegates committing to `git-commit` (haiku-tier sub-agent), then pushes via `scripts/push.sh`, which owns upstream tracking, the nothing-to-push case, and `--issue`-driven branch rename.
## Key Behaviors
- `scripts/push.sh --rename <branch>` renames and pushes with `--set-upstream` in one step; the *derivation* of the conforming branch name (`<type>/<issue>-slug`) stays with the agent — the script never invents names.
- "Nothing to commit or push" is a graceful no-op by contract, not an error — `git-commit-push-pr` relies on this to update a PR description without new commits.
- `--mansplain` and `--issue` are pass-through arguments: `--mansplain` forwards down to `git-commit`; `--issue` is consumed here (rename) but its number is re-derived upstream by `git-commit-push-pr` from the branch name.
## Changelog
| Date | Change | Ref |
|:-----|:-------|:----|
| 2026-06-12 | Initial version. Push/rename plumbing moved from SKILL.md prose into `scripts/push.sh` (relocated from git-commit-push-pr, extended with `--rename`). | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |