agentleFS
Sign inStart free
swarswar/nba_api/.claude/skills/release-pr/SKILL.md

release-pr

Skill3.9k starsChanged 11 days agoMITView on GitHub

Open the nba_api release PR - write the CHANGELOG.MD notes from the commits since the last tag, create the release/vX.Y.Z commit with scripts/gen-release.sh, push it, and open the "chore: release vX.Y.Z" PR. Use when the maintainer asks to prepare or start a release, open a release PR, or write release notes. Does not merge, tag, or publish.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run ./scripts/gen-release.sh --context and read the whole output.

    line 15
  2. Very specific:

    Write the notes to a file in your scratchpad (not in the repo), following the rules and format in RELEASING.md.

    line 16
  3. Very specific:

    Run ./scripts/gen-release.sh --notes <file> --yes (plus --bump, if any).

    line 18
  4. Distinctive:

    Stop there. Never merge the PR, push tags, create the GitHub release, or run the Release workflow.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Open the release PR for the next nba_api version. RELEASING.md is the source of truth; read its "Writing the release notes" section first and follow it exactly.

Bump override: $ARGUMENTS. If that's patch, minor, or major, add --bump <level> to both script runs below. If it's empty, use the version the commits imply. Anything else: stop and ask.

  1. Confirm you're on an up-to-date master with a clean working tree. If not, stop and say why.
  2. Run ./scripts/gen-release.sh --context and read the whole output.
  3. Write the notes to a file in your scratchpad (not in the repo), following the rules and format in RELEASING.md.
  4. Run ./scripts/gen-release.sh --notes <file> --yes (plus --bump, if any). If it warns that PRs are missing from the notes, decide whether each belongs, then git switch master, delete the release/vX.Y.Z branch, fix the notes, and re-run.
  5. Push the branch and open the PR: git push -u origin release/vX.Y.Z, then gh pr create --base master --title "chore: release vX.Y.Z" --body-file <file>. The body is the new CHANGELOG.MD section, followed by an "After merging" note: squash-merging starts the Release workflow (live canary, approval on the pypi environment, publish, then tag and GitHub release), so there are no manual tag or publish commands.
  6. Reply with the PR link and the new changelog section.

Stop there. Never merge the PR, push tags, create the GitHub release, or run the Release workflow. Merging is the maintainer's step, and it is what starts the release.

Download now (ZIP)

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. GetStream/stream-chat-flutter★ 1.1ksame name
    2. ashe-li/agent-skills★ 2same name
    3. fabiandistler/agents★ 2same 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 repository2 other files it gives its agents.

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