agentleFS
PydanticKnown publisherpydantic/pydantic-ai-harness/.agents/skills/pushing-commits-to-the-repo/SKILL.md

pushing-commits-to-the-repo

Skill954 starsChanged 4 months agoMITView on GitHub

What to do when you open a PR and every time you push -- label the PR, watch CI to

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. pydantic/pydantic-ai★ 21ksame name
    2. rohaquinlop/dsh-setup★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Leave nothing unstaged or uncommitted locally, unless the user's instructions override this.

    line 27
  2. Distinctive:

    Watch CI to a terminal state: Don't idle. If it fails, diagnose: fix if the failure is yours.

    line 30
  3. Distinctive:

    Never silently ignore a comment, and never resolve a thread without a reply.

    line 35
  4. Distinctive:

    Escalate real trade-offs, don't guess: If a comment needs a maintainer decision (a design choice, an API trade-off, a behavioral default), …

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. 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.
  3. 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.
  4. Repeat until CI is green and no comment is outstanding.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.