Run any Skill in Manus with one click

ticket-pr-lifecycle

Stars14

Forks0

UpdatedJune 17, 2026 at 19:25

Execute RPM GitHub issue-to-PR lifecycle work after take-ticket prepares context. Use for intake, issue reading, exploration handoff, draft PR setup, focused implementation, validation, PR checklist updates, and final audit; not for review feedback resolution.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

nerdchanii

nerdchanii/rpm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	ticket-pr-lifecycle
description	Execute RPM GitHub issue-to-PR lifecycle work after take-ticket prepares context. Use for intake, issue reading, exploration handoff, draft PR setup, focused implementation, validation, PR checklist updates, and final audit; not for review feedback resolution.

Ticket PR Lifecycle

Role

Run an RPM ticket from clean intake to ready PR while keeping behavior changes small and auditable. Use pr-review-resolution for review feedback.

Tool Surface

scripts/ticket-gen <issue-number-or-url> --format jsonl
scripts/ticket-gen <issue-number-or-url> --format json
bash scripts/check-workflow-intake.sh
bash scripts/check-workflow-final.sh <pr-number>
gh pr create --draft ...
gh pr view <pr> --json ...
gh pr edit <pr> --body-file <file>
narrow validation from AGENTS.md: cargo check, targeted cargo test, or cargo clippy --all-targets --all-features

Core Workflow

Run or receive the ticket-gen JSONL packet.
Run intake checks.
Use the ticket packet as the issue source of truth.
Use ticket-explorer for read-only exploration when non-trivial.
Classify SPEC impact and fixture needs.
Write a short plan: scope, SPEC status, likely files, validation, split decision.
Open a draft PR before implementation.
Implement one focused behavior change.
Run the narrowest relevant validation.
Update PR body/checklist when needed. Prefer pr-checklist-updater with gpt-5.4-mini and thinking=low; use thinking=medium only for non-mechanical body rewrites.
Hand review feedback to $pr-review-resolution.
Push final commits, mark ready, and run the final audit.

When To Read References

Read references/prompts-and-outputs.md when spawning ticket-explorer, creating the draft PR body, or returning lifecycle JSONL.

For command output or agent output consumed by another agent, use JSONL. Use Markdown only for human-facing PR bodies or summaries.

More from this repository

same repository

fixture-governance

nerdchanii/rpm

Create and review deterministic RPM fixtures for safe, non-mutating tests. Use when tests need package manifests, lockfiles, registry metadata, install projects, expected outputs, or regression fixtures.

2026-06-1714

pr-review-resolution

nerdchanii/rpm

Resolve RPM PR review feedback. Use after Codex or human PR comments arrive to collect review context, classify feedback, apply only accepted in-scope fixes, validate, and draft/create deferred follow-up issues when explicitly allowed.

2026-06-1714

spec-governance

nerdchanii/rpm

Keep SPEC.md authoritative for RPM contract-affecting changes. Use when code, reviews, or tickets may affect CLI behavior, lockfiles, manifests, semver, registry/cache/install/linking behavior, scripts, or diagnostics.

2026-06-1714

take-ticket

nerdchanii/rpm

Context handoff for RPM GitHub issue-to-PR work. Use when the user says to take a ticket, implement a GitHub issue, run the ticket loop, or coordinate RPM issue work; this skill prepares the shared context packet and delegates execution to ticket-pr-lifecycle, spec-governance, fixture-governance, and pr-review-resolution.

2026-06-1714

name	ticket-pr-lifecycle
description	Execute RPM GitHub issue-to-PR lifecycle work after take-ticket prepares context. Use for intake, issue reading, exploration handoff, draft PR setup, focused implementation, validation, PR checklist updates, and final audit; not for review feedback resolution.

Ticket PR Lifecycle

Role

Run an RPM ticket from clean intake to ready PR while keeping behavior changes small and auditable. Use pr-review-resolution for review feedback.

Tool Surface

scripts/ticket-gen <issue-number-or-url> --format jsonl
scripts/ticket-gen <issue-number-or-url> --format json
bash scripts/check-workflow-intake.sh
bash scripts/check-workflow-final.sh <pr-number>
gh pr create --draft ...
gh pr view <pr> --json ...
gh pr edit <pr> --body-file <file>
narrow validation from AGENTS.md: cargo check, targeted cargo test, or cargo clippy --all-targets --all-features

Core Workflow

Run or receive the ticket-gen JSONL packet.
Run intake checks.
Use the ticket packet as the issue source of truth.
Use ticket-explorer for read-only exploration when non-trivial.
Classify SPEC impact and fixture needs.
Write a short plan: scope, SPEC status, likely files, validation, split decision.
Open a draft PR before implementation.
Implement one focused behavior change.
Run the narrowest relevant validation.
Update PR body/checklist when needed. Prefer pr-checklist-updater with gpt-5.4-mini and thinking=low; use thinking=medium only for non-mechanical body rewrites.
Hand review feedback to $pr-review-resolution.
Push final commits, mark ready, and run the final audit.

When To Read References

Read references/prompts-and-outputs.md when spawning ticket-explorer, creating the draft PR body, or returning lifecycle JSONL.

For command output or agent output consumed by another agent, use JSONL. Use Markdown only for human-facing PR bodies or summaries.