agentleFS
Sign inStart free
polyaipolyai/adk/.claude/skills/open-pr/SKILL.md

open-pr

Skill83 starsChanged 39 days agoApache-2.0View on GitHub

Prepare and open a pull request on the polyai-adk repo, with checks run, the right conventional-commit title, the repo's PR template filled in and no internal references. Use when asked to open, create or raise a PR for ADK changes.

  • Commits and pushes

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-change, commit-push and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • thlaureSkill

    review-change

    Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

    Also in 4 projects that use this

  • DataCoveySkill

    commit-push

    Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.

    Also in 3 projects that use this

  • Codagent-AISkill

    implement-change

    Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

    Also in 3 projects that use this

  • saffron-healthSkill

    address-review

    Address PR review comments systematically. Use when responding to code review feedback on a pull request.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 17 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the ci-check skill and fix any failures.

    line 16
  2. Very specific:

    Run the review-pr skill on the local branch and fix any blocking findings.

    line 17
  3. Very specific:

    Read .github/PULL_REQUEST_TEMPLATE.md and fill in its sections only, without adding new ones.

    line 38
  4. Distinctive:

    Don't mention version numbers.

    line 47
  5. Very specific:

    If there's a related ticket, post it separately: gh pr comment <number> --body "<ticket link>".

    line 53

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “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

Open an ADK pull request

The PR title and description are public and become the release notes, so they matter as much as the code.

1. Check the branch

  • Work on a branch named <type>/<short-description>, never main.
  • Run the ci-check skill and fix any failures.
  • Run the review-pr skill on the local branch and fix any blocking findings.

2. Choose the title

Format: <type>[(scope)][!]: <what changed, in plain words>. Pick the type from what a user would notice:

The changeType
Anything a user can see: new command or flag, changed output, new on-disk shapefeat:
A bug fix with no new surfacefix:
Faster, same behaviourperf:
Breaks existing usageadd !, e.g. feat!:
Docs onlydocs:
CI, tooling, refactors, tests, internal-only changesci:, chore:, refactor:, test:

A user-visible change under a non-releasing type never ships a release, so when in doubt between feat and something else, it's feat.

3. Write the description

  • Read .github/PULL_REQUEST_TEMPLATE.md and fill in its sections only, without adding new ones. Changes covers the whole PR, and Test strategy says what was run and what was tried by hand.

  • Remove before posting:

    • ticket IDs (Linear ABC-123 style or any other tracker), from the title and body
    • real client or project names, account or project IDs
    • internal repos, services, tools, Slack channels, local paths

    Describe the problem generically instead.

  • Don't mention version numbers. Releases are automatic.

4. Open it

  • Show the title and description to the user and wait for their go-ahead.
  • gh pr create --draft --title "<title>" --body-file <file>
  • If there's a related ticket, post it separately: gh pr comment <number> --body "<ticket link>".
  • For stacked PRs, base each on the PR below it, and say in the description which PR to merge first.

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.

Check your setup, free