Skip to content
Skills Library
Programming · Automation

pr-lifecycle

/pr-lifecycle

Take a verified change from local branch through pull-request readiness, with optional merge only when the user explicitly authorizes it. Use for end-to-end GitHub PR work.

Licence
MIT
Last repository change
08.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Take a verified change from local branch through pull-request readiness, with optional merge only when the user explicitly authorizes it. Use for end-to-end GitHub PR work.

Original author description

Take a verified change from local branch through pull-request readiness, with optional merge only when the user explicitly authorizes it. Use for end-to-end GitHub PR work.

How it works

SKILL.md has no level-two headings · 15 lines, 172 words

SKILL.md preview
---
name: pr-lifecycle
description: Take a verified change from local branch through pull-request readiness, with optional merge only when the user explicitly authorizes it. Use for end-to-end GitHub PR work.
---

# Pull Request Lifecycle

Choose the requested stopping point first: local verification, PR opened, PR ready for human merge, or merged. Never assume merge authorization.

1. Inspect branch, diff, base, working-tree state, and original request. Preserve unrelated changes.
2. Run targeted tests and review the full diff. Resolve concrete issues before publication.
3. Confirm the intended repository, branch, visibility, title, and target. Create commits or push only when authorized.
4. Open or update a PR with a problem-first summary, behavior changes, tests actually run, and known limitations.
5. Monitor CI and review feedback only when requested or within the approved task. Use the PR watcher for check-state changes, but inspect review threads separately.
6. Fix validated findings, rerun relevant checks, and keep the PR description accurate.
7. Stop at the requested gate. Merge only with explicit authorization and after verifying required approvals, checks, mergeability, and target branch.

Never auto-merge because a check turned green. Do not force-push, dismiss reviews, or change repository settings without approval. Report the exact state observed from GitHub.

Versions

RepositoryScoreLicence
This page · voyager67/Agent-Workbench86MIT
onsager-ai/dev-skills100MIT
jl-cmd-projects/claude-dev-env96MIT

Database snapshot: 13.11.2026 · package version 2fd525be9a77 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85pull-request
    Defines typia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or merge one on unprompted initiative.
  • 95implement-spec
    Use when a ticket DAG from a complete specification needs parallel execution into a verified integration branch, with an optional green draft pull request or merge request on explicit approval. Not for a settled ticket with no spec and not for ticket decomposition.
  • 100pr-description
    Use when writing or updating a pull request or merge request description for the current branch, for GitHub, GitLab, or Bitbucket.
  • 85pull-request
    Defines typia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or merge one on unprompted initiative.
  • 100github-pr-workflow
    Use when creating, updating, or managing pull requests — automates the full PR lifecycle (open, review requests, labels, merge) via GitHub MCP
  • 85pull-request
    Defines ttsc branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or merge one on unprompted initiative.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.