pushing-commits-to-the-repo

Manages the full pull request lifecycle from opening through CI monitoring and comment triage.

19.6k|2.6k|Updated Jun 21, 2024
One-click install
npx skills add https://github.com/pydantic/pydantic-ai --skill pushing-commits-to-the-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pushing-commits-to-the-repo
Source: https://github.com/pydantic/pydantic-ai/tree/main/.agents/skills/pushing-commits-to-the-repo
Command: npx skills add https://github.com/pydantic/pydantic-ai --skill pushing-commits-to-the-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Opening a pull request is not the end of the work — CI failures, review comments, and stale metadata all need continuous attention. This Skill enforces a disciplined loop so a PR is only considered done when CI is green and every comment has been triaged.

Core Features & Use Cases

  • Structured PR authoring: Writes titles and bodies following the repo's AGENTS.md template, including call-path diffs, verification sections, and correct label application via gh label list.
  • Pre-push review gate: Runs a pre-push-review before every push, forbids force-pushes on open PR branches, and requires a clean working tree.
  • Post-push loop: Watches CI to a terminal state, triages every bot and human comment (fix, reply, react), escalates design trade-offs to maintainers, and optionally triggers a deep douwebot review.
  • Use Case: After pushing a feature branch, the Skill watches CI, fixes a failing test, replies to three review comments with code evidence, applies the feature label, and only hands the PR back once a fresh subagent confirms the title and body are current.

Quick Start

Open a pull request for my current branch and keep iterating on it until CI is green and every review comment is resolved.

Frequently Asked Questions about pushing-commits-to-the-repo

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

FAQPage Schema
How do I manage a pull request until it is ready to merge?

Open the PR with a compliant title and body, apply the right labels, then loop: watch CI to a terminal state, triage every comment by fixing or rebutting with evidence, and repeat until CI is green and no comment is unresolved.

How do I apply labels to a GitHub PR with the gh CLI?

First run `gh label list --limit 100` to fetch the real label set, since guessed labels silently fail. Then apply with `gh pr edit <number> --add-label <label>`, choosing a type label like bug or feature plus a topic label.

Can I force-push to an open pull request branch?

No. Force-pushing invalidates previous reviews. Push follow-up commits instead so earlier reviews remain valid; maintainers can squash the commits when merging.

What should I do when a PR review comment requires a design decision?

Escalate rather than guess. Post a comment with the background, your reasoning, the decision needed, trade-offs of each option, and a recommendation, then poll every 30 minutes for a maintainer reply before continuing.

When should I trigger a douwebot deep review on a PR?

Apply the douwebot label only after CI is green and all comments are triaged, since it reviews the diff exactly once. Skip it for trivial changes like typo fixes, but use it for features, behavior changes, and public API surface.