skills.rest
joestump
joestumpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

enrich

Append Branch naming and PR Convention blocks to tracker issues for a SPEC.

30|2|Updated Feb 13, 2026
Search Tags:#automation#workflow#branch-naming#issue-tracker#enrich#pr-conventions
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill enrich-joestump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enrich
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/enrich
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill enrich-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retroactively add Branch naming and PR Convention sections to existing tracker issues to standardize developer workflows and reduce manual edits.

Core Features & Use Cases

  • Append ### Branch and ### PR Convention sections to issues that reference a SPEC, ensuring idempotence.
  • Respect plugin configuration to determine branch prefixes and PR close/reference keywords.
  • Seamlessly handle multiple trackers and provide dry-run reporting when requested.

Quick Start

Invoke the enrich skill with a SPEC-XXXX or spec-name to attach Branch and PR Convention sections to relevant tracker issues.

Frequently Asked Questions about enrich

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

FAQPage Schema
How do I add branch naming conventions to existing tracker issues?▼

The enrich skill standardizes developer workflows by appending Branch and PR Convention sections to existing tracker issues. It reduces manual edits and ensures consistent PR conventions across multiple trackers based on your SPEC details.

How do I standardize PR conventions across multiple issue trackers?▼

The enrich skill reads SPEC details and plugin configuration to generate correct PR Convention sections across multiple trackers. It applies these sections idempotently, ensuring existing issues are updated safely without duplicating content or requiring manual edits.

Can I preview branch naming changes before applying them to issues?▼

You can preview branch naming changes by enabling the dry-run option in the enrich skill. This generates a report of proposed outcomes without modifying tracker issues, allowing you to verify the appended sections before committing to actual changes.

Does the issue enrichment process support idempotent updates?▼

The issue enrichment process supports idempotent updates. The enrich skill safely appends Branch and PR Convention sections to issues referencing a SPEC without duplicating content, using a try-then-create approach for labels and reporting all outcomes.

What is the best way to automate adding SPEC details to tracker issues?▼

The best way to automate adding SPEC details is invoking the enrich skill with a SPEC-XXXX or spec-name input. It reads plugin configuration to determine branch prefixes and PR close/reference keywords, applying them automatically across relevant trackers.

Why does branch naming automation need plugin configuration?▼

Branch naming automation requires plugin configuration to determine correct branch prefixes and PR close/reference keywords. The enrich skill reads this configuration to generate accurate, standardized sections that match your project's established conventions across multiple trackers.

Related Skills

Explore More Software Engineering Skills→
t0labt0lab
2

branch-strategy

Enforce Git branch naming patterns and PR size limits.

Official
Intermediate
joestumpjoestump
30

work

Coordinate parallel tracker issue implementation via deterministic git worktrees and automated PRs.

Community
Advanced
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
CodenburgCodenburg

branch-pr

Validate pull requests against approved issues and branch naming conventions.

Community
Intermediate