generic-automation-and-it/smooth-ai-stockanalysis / .agents/skills/git-commit-push-pr
git-commit-push-pr
VerifiedCommit current changes, push to remote, and create or update a pull request on GitHub. Use when making changes and preparing a complete pull request for review.
| File | Kind | Size |
|---|---|---|
| AGENTS.md | markdown | 1.9 KB |
| SKILL.md | skill md | 10.3 KB |
| agents/openai.yaml | config | 322 B |
| scripts/get-base-branch.shexecutable | script | 538 B |
| scripts/get-pr-metadata.shexecutable | script | 1.1 KB |
AGENTS.md
View on GitHub# git-commit-push-pr — AGENTS.md
## TL;DR
Top of the git skill chain; PRs are **draft by default**, titles follow `<type>[{ticket}]: <description>`, and the branch name is the single source for the issue number (via `scripts/get-pr-metadata.sh`).
## System Context
```mermaid
sequenceDiagram
participant PR as git-commit-push-pr
participant Push as git-commit-push (sub-agent)
participant Commit as git-commit (sub-agent)
participant GH as GitHub (gh CLI)
PR->>Push: delegate commit+push (forwards --issue, --mansplain)
Push->>Commit: delegate commit (forwards --mansplain)
Push->>GH: push (scripts/push.sh, optional rename)
PR->>PR: get-pr-metadata.sh → type/issue/pr_title_prefix
PR->>GH: gh pr create/edit (template body, Closes #issue)
PR->>GH: verify body sections (gh pr view)
```
## Non-Negotiables
- **PR body is ALWAYS the repo template** (`.github/pull_request_template.md`) — no custom formats; updates are full replacements that must preserve the existing AI Review Notes section.
- **Never guess a ticket number.** Empty `issue` from the metadata script on a ticketless branch means: skip the `Closes #` link gracefully, don't invent one.
## Key Behaviors
- `scripts/get-pr-metadata.sh` parses the branch per git-policy and returns `pr_title_prefix` (`<type>[<issue>]` / `<type>[NO-TICKET]`); an **empty `type` signals a non-conforming branch**, which is the trigger to derive the type from commits instead. The legacy version of this script used the retired `Bugfix`/`Hotfix`/JIRA-ticket vocabulary — don't reintroduce it.
- PR titles become squash-commit messages on `main`; that's why the title gate is stricter than the commit gate.
## Changelog
| Date | Change | Ref |
|:-----|:-------|:----|
| 2026-06-12 | Initial version. `get-pr-metadata.sh` rewritten to current convention and wired into SKILL.md; `push.sh` relocated to git-commit-push; redundant gh-CLI reference section removed. | |
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 |