pr-init

This is a placeholder for the actual response text.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-init
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/pr-init
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bootstraps PR lifecycles by creating or bootstrapping a GitHub issue, generating the canonical local source prompt, and seeding the initial root task bundle.

Core Features & Use Cases

  • Create or bootstrap a GitHub issue for the PR lifecycle.
  • Seed the canonical local source issue prompt and the root task bundle (stp.md, sip.md, sor.md).
  • Validate bootstrap state and stop before branch creation, worktree creation, or implementation work.
  • Support two modes: create_and_bootstrap for new issues and bootstrap_existing_issue for existing issues.

Quick Start

Bootstrap a PR lifecycle by creating or bootstrapping an issue, then seed the canonical prompt and initial bundle, and stop before any branch or worktree creation.

Frequently Asked Questions about pr-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a GitHub issue and seed a local source prompt for a PR lifecycle?

To bootstrap a PR lifecycle, you create or bootstrap a GitHub issue, generate the canonical local source prompt, and seed the initial root task bundle containing stp.md, sip.md, and sor.md before any branch creation.

What files are generated when seeding a root task bundle for a new issue?

Seeding a root task bundle generates stp.md, sip.md, and sor.md. These files establish the canonical local source prompt and initial task state for deterministic execution before any branch or worktree creation.

Can I bootstrap an existing GitHub issue or do I need to create a new one?

You can bootstrap both new and existing GitHub issues. For new issues, provide a title and labels; for existing issues, supply the issue number to seed the canonical prompt and root task bundle.

Does the PR bootstrap process create a Git branch or worktree automatically?

No, the bootstrap process validates the bootstrap state and deliberately stops before any branch or worktree creation, ensuring the issue and source prompt are correctly seeded before implementation work starts.

What inputs do I need to provide to bootstrap a PR lifecycle deterministically?

You need to provide a repo_root and an issue target, which includes a title and labels for new issues or an issue number for existing ones, allowing the process to follow repository templates for deterministic execution.

When should I use an automated PR lifecycle bootstrap instead of manual issue setup?

Use an automated PR lifecycle bootstrap when you need deterministic execution that follows repository standard templates and policy, ensuring consistent seeding of stp.md, sip.md, and sor.md across multiple issues without manual formatting.