Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers.
Install Pushing Commits To The Repo
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .claude/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .claude/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .agents/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .agents/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .cursor/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .cursor/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pydantic/pydantic-ai-harness.git --path .agents/skills/pushing-commits-to-the-repo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .gemini/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .gemini/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .github/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .github/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pydantic/pydantic-ai-harness pushing-commits-to-the-repo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/pydantic-ai-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pushing-commits-to-the-repo .opencode/skills/pushing-commits-to-the-repo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pushing-commits-to-the-repo" agent skill from https://github.com/pydantic/pydantic-ai-harness/tree/main/.agents/skills/pushing-commits-to-the-repo into .opencode/skills/pushing-commits-to-the-repo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pushing-commits-to-the-repo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pushing-commits-to-the-repo- GitHub stars
- 952
- Token cost
- ~566 tokens
- SKILL.md length
- 300 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers.
- Works in 4 steps: Watch CI to a terminal state. Don't… → Triage every comment (bots and humans… → Escalate real trade-offs, don't guess.… → …
- Push a commit to one
- SKILL.md covers When you open the PR, Before you push and After you push — the loop
- Calls gh
What it does
Pushing Commits To The Repo is an agent skill from pydantic/pydantic-ai-harness, published by the product's own GitHub organization. What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers. Use whenever you open a PR or push a commit to one.
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: Your agent's favorite harness, built on Pydantic AI. The licence is MIT.
When your agent uses it
- Push a commit to one
- Tasks that involve Pull requests
Example prompts
- “/pushing-commits-to-the-repo”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Watch CI to a terminal state. Don't idle. If it fails, diagnose: fix if the failure is
- Triage every comment (bots and humans alike). For each one
- Escalate real trade-offs, don't guess. If a comment needs a maintainer decision (a design
- Repeat until CI is green and no comment is outstanding.
What it can do on your machine
Read from SKILL.md and the folder at commit 4399efa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pushing Commits To The Repo loads about 566 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 300 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pydantic/pydantic-ai-harness at commit 4399efa, republished under its MIT licence (© pydantic). 300 words, ~566 tokens.
Download SKILL.mdSave it as
.claude/skills/pushing-commits-to-the-repo/SKILL.md (or your agent's skills folder).- name
- pushing-commits-to-the-repo
- description
- What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers. Use whenever you open a PR or push a commit to one.
pushing-commits-to-the-repo
Pushing starts a loop; it does not end the task. Work stops only when CI is green AND no comment is left unresolved.
When you open the PR
Apply a label -- the repo triages and filters by them. Fetch the real list first with
gh label list --limit 100, because the set changes and a guessed label silently fails to apply.
Pick the one naming what the PR is (bug, enhancement, documentation) and add a topic label
where one fits (capability, primitive, agent-feature, core-change, code-mode, media,
externalization, ...): gh pr edit <number> --add-label <label>.
Labelling needs triage permission on the repo. If it fails, quote the actual error rather than concluding you lack permission.
Before you push
- Attempt the push. If it fails, read the real error — do not preemptively decide you lack permission from a flag or setting.
- Leave nothing unstaged or uncommitted locally, unless the user's instructions override this.
After you push — the loop
- Watch CI to a terminal state. Don't idle. If it fails, diagnose: fix if the failure is yours; if it's a known flake or pre-existing on main, say so with evidence.
- Triage every comment (bots and humans alike). For each one:
- Valid → fix it, then reply saying what changed, and react 👍.
- Invalid → reply explaining concretely why (with code evidence), and react 👎.
- Never silently ignore a comment, and never resolve a thread without a reply.
- Escalate real trade-offs, don't guess. If a comment needs a maintainer decision (a design choice, an API trade-off, a behavioral default), leave a comment containing: the background, your reasoning, the decision that needs making, the trade-offs (pros/cons of each option), and your recommendation. Then poll every 30 minutes for a reply and continue when it lands.
- Repeat until CI is green and no comment is outstanding.
© pydantic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/pushing-commits-to-the-repo of pydantic/pydantic-ai-harness.
Open the folder on GitHubat commit 4399efa
Compare with similar skills
Pushing Commits To The Repo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pushing Commits To The Repo this skillpydantic/pydantic-ai-harness | 952 | — | ~566 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from pydantic/pydantic-ai-harness
- Official
Adopt PR Branch Context
pydantic/pydantic-ai-harness
Fills in issue-brief.md and pr-decisions.md for an existing pull request, so you can pick up a PR mid-flight with its linked issue and past review decisions summarized.
- Official
Branch Context Handoff
pydantic/pydantic-ai-harness
Keeps a branch-local issue brief, decision log and session handoffs so a pull request's context survives across separate agent sessions.
Related
Categories
Questions about Pushing Commits To The Repo
What does Pushing Commits To The Repo do?
What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers. Pushing Commits To The Repo is an agent skill from pydantic/pydantic-ai-harness, published by the product's own GitHub organization. What to do when you open a PR and every time you push -- label the PR, watch CI to green, triage every review comment to a reply and a reaction, and escalate genuine design trade-offs to maintainers.
When should I use Pushing Commits To The Repo?
Pushing Commits To The Repo fits situations like: push a commit to one; tasks that involve Pull requests.
How do I install Pushing Commits To The Repo in Claude Code?
Run `npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a claude-code`. Or copy the skill folder (.agents/skills/pushing-commits-to-the-repo in pydantic/pydantic-ai-harness) into .claude/skills/pushing-commits-to-the-repo in your project. Claude Code loads it when a task matches its description.
How do I install Pushing Commits To The Repo in Codex?
Run `npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a codex`. Or copy the skill folder (.agents/skills/pushing-commits-to-the-repo in pydantic/pydantic-ai-harness) into .agents/skills/pushing-commits-to-the-repo in your project. Codex loads it when a task matches its description.
Can I use Pushing Commits To The Repo in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pydantic/pydantic-ai-harness --skill pushing-commits-to-the-repo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pushing-commits-to-the-repo, .gemini/skills/pushing-commits-to-the-repo, .github/skills/pushing-commits-to-the-repo and .opencode/skills/pushing-commits-to-the-repo in your project.
What does Pushing Commits To The Repo need to run?
Going by SKILL.md and its folder, Pushing Commits To The Repo needs the command-line tools its instructions call (gh).
Does Pushing Commits To The Repo access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pushing Commits To The Repo safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pushing Commits To The Repo use?
Pushing Commits To The Repo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pushing Commits To The Repo use?
About 566 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pushing Commits To The Repo?
Skills that share tags, products or a category with Pushing Commits To The Repo: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pushing Commits To The Repo?
pydantic (a GitHub organization, an official publisher) maintains it in pydantic/pydantic-ai-harness, which has 952 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 2, 2026.
Source: pydantic/pydantic-ai-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.