Saucebox Registry
← Browse

@majiayu000/pr

B

Commit changes, bump version, update changelog, and open a PR

skillclaude

Install

agr install @majiayu000/pr --target claude

Writes 2 files into .claude/skills/, pinned to git-c8635963.

  • .claude/skills/pr/SKILL.md
  • .claude/skills/pr/metadata.json

Document

name: pr description: Commit changes, bump version, update changelog, and open a PR

/pr - Prepare and Submit Changes

Purpose

Commit changes to a feature branch, bump version if needed, update changelog, and open a PR.

Before Starting

  • Check for uncommitted changes: git status --porcelain
  • Ensure tests pass: make test or equivalent
  • Confirm current branch (create one if on main)

Process

  1. Create or verify feature branch

    If on main, create a branch from the work context:

    git checkout -b <descriptive-branch-name>

  2. Stage and commit changes

    Use the user's git identity (never sign as Claude, no Co-authored-by). Write conventional commit messages:

    • feat: add remote file sync
    • fix: resolve timeout on large files

  3. Bump version if warranted

    • Bug fixes → patch
    • New features → minor
    • Breaking changes → major

    Update version in pyproject.toml (or equivalent).

  4. Update CHANGELOG.md

    Use /changelog skill to generate entry if changes are user-facing.

  5. Push and create PR

    git push -u origin <branch>
gh pr create --fill

    PR description should summarize changes. Link issues if referenced in commits.

Notes

  • Don't add "Signed-off-by" or "Co-authored-by: Claude" trailers
  • Ask before force-pushing
  • If tests fail, stop and report

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-c86359632a932026-07-31