beads-pr-prepare

dikini's avatarfrom dikini

Prepare a pull request title/body from a Beads task (optionally using gh)

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 25, 2025⬇️1downloads
[Developer Tools]

When & Why to Use This Skill

This Claude skill automates the transition from task management to version control by generating Pull Request (PR) titles and descriptions directly from Beads task data. It streamlines the developer workflow by ensuring PRs are consistently formatted, correctly linked to project tasks, and can optionally be submitted via the GitHub CLI, significantly reducing manual administrative overhead.

Use Cases

  • Standardizing PR Metadata: Automatically generate consistent PR titles and markdown bodies using predefined templates and task data from the Beads system.
  • Project Traceability: Ensure every Pull Request is accurately linked to its corresponding task ID (e.g., bd-a3f8) to maintain a clear audit trail between requirements and code changes.
  • End-to-End Workflow Automation: Use the integrated GitHub CLI (gh) support to not only prepare but also create or update pull requests directly through the agent interface.
namebeads-pr-prepare
descriptionPrepare a pull request title/body from a Beads task (optionally using gh)

Beads: prepare PR

Goal

Given a Beads task id (e.g. bd-a3f8), prepare a PR title and markdown body that references the task.

Inputs

  • bead_id (required)
  • Whether to use gh to create/update PR (optional; only if available + authenticated)

Procedure

  1. Fetch task details:
bd show <bead_id> --json
  1. Draft PR metadata:
  • Title: keep it short; include bead id prefix (e.g. bd-a3f8: <title>)
  • Body: use the template at:
    • ./.goose/skills/beads-pr-prepare/templates/pr-body.md
  1. If gh is available and authorized, offer optional automation:
  • Create PR (example):
gh pr create --title "<title>" --body-file <path-to-generated-body>

Output

  • Always return:
    • PR title
    • PR body markdown
  • If gh automation is used, also return:
    • PR URL

Notes

  • If --json isn’t supported, fall back to bd show <bead_id> and extract details from text.
  • Running gh should be explicit: only do it when the user asks to create the PR.