Pr branch

Skill mattjaikaran/meridian/skills/pr-branch

Skill that gives AI coding agents persistent memory and quality enforcement

Install

npx -y skills add mattjaikaran/meridian --skill pr-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

/meridian:pr-branch — Create Clean PR Branch

Create a PR-ready branch with only code-relevant commits, filtering out .planning/ and .meridian/ changes.

Arguments

<slug> (required) — Feature name for the branch (creates pr/<slug>)
--base <branch> — Base branch to diff against (default: main)

Procedure

Step 1: Identify Code Commits

PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c "
from scripts.pr_branch import filter_commits
commits = filter_commits('main')
print(f'{len(commits)} code commits found')
for sha in commits:
    print(sha)
"

If no code commits found, warn user and stop.

Step 2: Create PR Branch

PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c "
from scripts.pr_branch import create_pr_branch
branch = create_pr_branch('<slug>', 'main')
print(f'Created branch: {branch}')
"

Step 3: Verify Branch

git log --oneline main..pr/<slug>
git diff --stat main..pr/<slug>

Step 4: Push (optional)

git push -u origin pr/<slug>

Notes

Original branch is preserved — this is non-destructive
Uses cherry-pick internally, so conflicts are possible on divergent histories
If cherry-pick fails, the partial branch is cleaned up automatically

Gives 0 of the 12 instructions most pr commit review skills give in 343 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

use conventional commits formatin 127 of 888, across 115 files
keep subject line under 72 charactersin 62 of 888, across 48 files
delete branches after mergein 51 of 888, across 38 files
use imperative mood in subject linein 51 of 888, across 42 files
use imperative mood in commit messagesin 44 of 888
verify directory is ignored before creating worktreein 43 of 888, across 12 files
generate a conventional commit messagein 43 of 888
add unignored worktree directories to gitignorein 42 of 888, across 10 files
make atomic commitsin 39 of 888, across 27 files
run tests before committingin 36 of 888, across 25 files
verify clean test baselinein 35 of 888, across 9 files
split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

filter out planning and metadata changes
create a branch prefixed with pr
push the branch optionally
preserve the original branch

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.