How do I install the Work Pr skill?

Run npx skillmds@latest add django-oauth/work-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Work Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Work Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Work Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Work Pr?

django-oauth (@django-oauth) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Work Pr by django-oauth — Agent Skill

Name: Work Pr
Author: django-oauth

File contents

Work a PR

One issue → one branch → one PR. Drive to green CI with no open review threads.

Open

Branch off master: claude/fix-<issue>-<slug>.
Implement the smallest correct change. Add a regression test that fails before, passes after.
Add a ## [unreleased] entry in CHANGELOG.md referencing #<issue> (skip for changes that aren't user-relevant, e.g. tooling).
Lint and run related tests locally: ruff check + ruff format --check, and DJANGO_SETTINGS_MODULE=tests.settings python -m pytest <paths>.
Commit, push -u. Open the PR filling .github/pull_request_template.md; Fixes #<issue>.
Request a Copilot review. Subscribe to PR activity. Arm a ~1h fallback check-in.

On each CI / review event

Fix if confident and small; rebut if the suggestion is wrong; skip duplicates/no-ops.
Push the fix (prefer a follow-up commit; only force-push when you intentionally rebased, and always use --force-with-lease).
Reply on each review thread, then resolve it — not a PR-level comment.
Re-request Copilot review. Repeat until CI green and Copilot has no comments.

When master advances

When the branch falls behind master while the PR is open — it shows merge conflicts against the base, or CI ran against a now-stale base — rebase onto the latest master and force-push with lease:

git fetch upstream
git rebase --autostash upstream/master
# resolve conflicts, re-run the affected tests
git push --force-with-lease

Rules

Reply on threads only; no PR-level status comments.
Never git add -A — stage explicit paths, so stray untracked files (local venvs, build output, editor scratch) are never committed.
Don't poll with sleep; events + the fallback check-in wake you. Re-arm it silently if nothing changed.
Don't self-merge. A subscription ends only when the PR is merged/closed.

---name: work-prdescription: Open and drive a single-issue PR to merge-ready in django-oauth-toolkit. Use when implementing a bug/feature that ships as its own PR, or when babysitting an open PR through CI and Copilot review.---# Work a PROne issue → one branch → one PR. Drive to green CI with no open review threads.## Open1. Branch off `master`: `claude/fix-<issue>-<slug>`.2. Implement the smallest correct change. Add a regression test that **fails before, passes after**.3. Add a `## [unreleased]` entry in `CHANGELOG.md` referencing `#<issue>` (skip for changes that aren't user-relevant, e.g. tooling).4. Lint and run related tests locally: `ruff check` + `ruff format --check`, and `DJANGO_SETTINGS_MODULE=tests.settings python -m pytest <paths>`.5. Commit, push `-u`. Open the PR filling `.github/pull_request_template.md`; `Fixes #<issue>`.6. Request a Copilot review. Subscribe to PR activity. Arm a ~1h fallback check-in.## On each CI / review event- **Fix** if confident and small; **rebut** if the suggestion is wrong; **skip** duplicates/no-ops.- Push the fix (prefer a follow-up commit; only force-push when you intentionally rebased, and always use `--force-with-lease`).- **Reply on each review thread, then resolve it** — not a PR-level comment.- Re-request Copilot review. Repeat until **CI green and Copilot has no comments**.## When master advancesWhen the branch falls behind master while the PR is open — it shows merge conflicts against the base, or CI ran against a now-stale base — rebase onto the latest master and force-push with lease:```git fetch upstreamgit rebase --autostash upstream/master# resolve conflicts, re-run the affected testsgit push --force-with-lease```## Rules- Reply on threads only; no PR-level status comments.- Never `git add -A` — stage explicit paths, so stray untracked files (local venvs, build output, editor scratch) are never committed.- Don't poll with sleep; events + the fallback check-in wake you. Re-arm it silently if nothing changed.- Don't self-merge. A subscription ends only when the PR is merged/closed.

Frequently asked questions

Work Pr