Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jl-cmd/claude-dev-envnpx agentmods add skills/jl-cmd/claude-dev-env/pr-lifecycleWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-lifecycle)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-lifecycle"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-lifecycle/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-lifecycle"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.05813 |
| Opus 5.5 | $0.00008 | $0.02325 |
| Sonnet 5.5 | $0.00004 | $0.01163 |
| Haiku 4.5 | $0.00002 | $0.00581 |
Grade A, and why
pr-lifecycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull request lifecycle
Git workflow
User-level rule: applies to every git repo that uses GitHub with gh. Small or non-primary repos follow the same rule unless the user says otherwise in the session.
Workflow decision tree
When to use stacked PRs: Feature B depends on Feature A's implementation
When to extract shared infrastructure first: Multiple features need same utilities/helpers
Extract Shared Infrastructure Pattern:
- Create infrastructure PR with only shared code
- Get reviewed and MERGE infrastructure first
- Launch parallel feature PRs that use merged infrastructure
Pull request submission rules
Open every pull request ready for review. Pass --draft only when the owner asks
for a draft.
A release bot's PR body is machine input. Leave it alone. Release automation reads back the body of its own merged pull request to decide it owns that merge. Rewriting the body, or trimming its header or footer, makes the bot treat the merge as somebody else's work: it cuts no tag, the publish job skips, and it opens one more release pull request on the next run. The merge stays in the repository. No tag is cut and the package never publishes.
Spot one by its head branch, which starts release-please--branches--, or by a body that
opens with the bot's own marker line. The description rules in this file, the
pstack:poteto-agent writing brief, and the house wording style all step aside for it. The
failure signature in the release job log reads
could not parse pull request body as a release PR.
pstack:poteto-agent writes a title and body from the diff when you want one.
Publish the title and body file through
~/.agents/skills/pull-request/scripts/pull_request.py. That path is under the
agents home. A worktree holds no .agents/ copy.
Resolve the active managed root (CLAUDE_CONFIG_DIR when set, ~/.claude
otherwise), then run <managed-root>/scripts/durable_post_lint.py before any
pull request, issue, or GitHub MCP post. The linter checks the action-specific
title, body, and volatile-path rules before credential lookup or network
access.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 14d ago First seen · 471 lines · 19 tokens per session scan A dc297db980be
pr-lifecycle is a skill published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 5,813 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
plate
Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…
git-iris
Use this skill when generating commit messages, pull request descriptions, release notes, changelogs, or code reviews in a repository where git-iris is available. Activates on requests like "commit this", "write a commit message", "draft a PR", "generate release notes", "write a changelog", or "review my changes" when…
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
mx-pr
Draft a pull request from the feature spec and git log, then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
github
GitHub-centric templates — pull requests, issue triage, repo automation.