← ClaudeAtlas

prlisted

Prepare, open, update, or assess a pull request, including checks, changesets, title, template, and CI.
stijnvanhulle/agents · ★ 1 · Data & Documents · score 74
Install: claude install-skill stijnvanhulle/agents
# PR Take a branch to merge-ready. Work in order; disclose any unfinished step in the PR body. ## 1. Branch Never commit to `main`. Check where you are, and branch from an up-to-date `main` when still on it: ```bash git status git branch --show-current git fetch origin main git switch -c <category>/<ISSUE-REF>_<branch-name> origin/main ``` Use the `branch` skill's `<category>/<ISSUE-REF>_<slug>` shape. Omit the reference when none exists. ## 2. Checks ```bash pnpm format && pnpm lint:fix && pnpm typecheck && pnpm test ``` Also run `pnpm build` after package-source changes. Fix failures at the source; never weaken a type or rule, or skip a test. ## 3. Changeset Run the `changeset` skill for versioned package changes. Docs, CI, and tests alone need none. ## 4. Commit Use one imperative Conventional Commit per logical change, under 72 characters, no period. Review `git diff --cached`. Never commit secrets or generated output; generate lockfiles with pnpm. ## 5. Title and body Title: imperative Conventional Commit, under 72 characters, no period. Derive the type from the change or issue label, not `feature`/`hotfix`. Put `Closes #123` in the body. Fill `.github/pull_request_template.md` without deleting sections: - **Changes:** what changed and why, in 1–3 sentences. - **How to test:** three clean-checkout steps ending in the expected result. If the diff cannot supply them, use the `ask` skill. Add screenshots for visible changes. - **Checklist:** check only wha