How do I install the Issue Pr Lifecycle Agent skill?

Run npx skillmds@latest add richfrem/issue-pr-lifecycle-agent 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 Issue Pr Lifecycle Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue Pr Lifecycle Agent?

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 Issue Pr Lifecycle Agent free to use?

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

Who published Issue Pr Lifecycle Agent?

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

Issue Pr Lifecycle Agent by richfrem

Name: Issue Pr Lifecycle Agent
Rating: 4.5 (4 reviews)
Author: richfrem

Issue Pr Lifecycle Agent

Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).

richfrem Updated Sep 10, 2026

File contents

Issue PR Lifecycle Agent (`issue-pr-lifecycle-agent`)

Routing Directive: USE ONLY when orchestrating or dry-running the full lifecycle flow (Issue -> Worktree -> PR -> Close resolution). DO NOT USE for individual isolated worktree setup (use issue-worktree-agent instead), task scratchpads (use task-agent instead), or friction logging (use github-issue-agent instead).

The issue-pr-lifecycle-agent skill connects git worktree execution with GitHub CLI operations (gh pr create, gh issue close) into a single, verifiable workflow pipeline.

Safety & Security Contracts

Dry-Run by Default: Execution defaults to dry-run payload generation (--execute flag required for live changes).
Linked Resolution: Automatically appends Closes #NNN to PR bodies to enforce automatic resolution tracking.
Structured Flow: Sequence: Worktree Creation -> PR Submission -> Issue Closure -> Worktree Cleanup.

Usage catalog

Orchestrate End-to-End Lifecycle

Helper Script: plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py

CLI Usage:

# Dry-run payload generation for Issue #42:
python3 plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py --issue 42 --title "Fix login bug" --body "Resolves crash on empty password"

# Live execution of end-to-end lifecycle:
python3 plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py --issue 42 --title "Fix login bug" --body "Resolves crash on empty password" --execute

Python API Interface

from plugins.dev_utils.skills.issue_pr_lifecycle_agent.scripts.issue_pr_orchestrate import (
    orchestrate_lifecycle,
    generate_lifecycle_payload,
)

# Generate dry-run payload
payload = generate_lifecycle_payload(issue_number=42, title="Fix bug", body="Fixes #42")

# Orchestrate lifecycle
res = orchestrate_lifecycle(issue_number=42, title="Fix bug", body="Fixes #42", dry_run=False)

---name: issue-pr-lifecycle-agentdescription: Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).---# Issue PR Lifecycle Agent (`issue-pr-lifecycle-agent`)> **Routing Directive:** USE ONLY when orchestrating or dry-running the full lifecycle flow (Issue -> Worktree -> PR -> Close resolution). DO NOT USE for individual isolated worktree setup (use `issue-worktree-agent` instead), task scratchpads (use `task-agent` instead), or friction logging (use `github-issue-agent` instead).The `issue-pr-lifecycle-agent` skill connects git worktree execution with GitHub CLI operations (`gh pr create`, `gh issue close`) into a single, verifiable workflow pipeline.---## Safety & Security Contracts1. **Dry-Run by Default:** Execution defaults to dry-run payload generation (`--execute` flag required for live changes).2. **Linked Resolution:** Automatically appends `Closes #NNN` to PR bodies to enforce automatic resolution tracking.3. **Structured Flow:** Sequence: Worktree Creation -> PR Submission -> Issue Closure -> Worktree Cleanup.---## Usage catalog### Orchestrate End-to-End Lifecycle- **Helper Script:** `plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py`- **CLI Usage:** ```bash # Dry-run payload generation for Issue #42: python3 plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py --issue 42 --title "Fix login bug" --body "Resolves crash on empty password" # Live execution of end-to-end lifecycle: python3 plugins/dev-utils/skills/issue-pr-lifecycle-agent/scripts/issue_pr_orchestrate.py --issue 42 --title "Fix login bug" --body "Resolves crash on empty password" --execute ```---## Python API Interface```pythonfrom plugins.dev_utils.skills.issue_pr_lifecycle_agent.scripts.issue_pr_orchestrate import ( orchestrate_lifecycle, generate_lifecycle_payload,)# Generate dry-run payloadpayload = generate_lifecycle_payload(issue_number=42, title="Fix bug", body="Fixes #42")# Orchestrate lifecycleres = orchestrate_lifecycle(issue_number=42, title="Fix bug", body="Fixes #42", dry_run=False)```

Frequently asked questions