skills.rest
tigredonorte
tigredonorteCOMMUNITY
Explore all skills by this author →
GitHub

work-pr

Update PR descriptions and attach visual documentation for Jira-tied tasks.

Updated Feb 25, 2026
Search Tags:#jira#pr#pull-request#state-machine#workflow-engine#visual-documentation
One-click install
npx skills add https://github.com/tigredonorte/claude-plugin-work --skill work-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-pr
Source: https://github.com/tigredonorte/claude-plugin-work/tree/main/skills/work-pr
Command: npx skills add https://github.com/tigredonorte/claude-plugin-work --skill work-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updates PR descriptions and adds visual documentation for Jira-tied tasks. Automating PR updates reduces manual toil and keeps stakeholders aligned with current implementation details.

Core Features & Use Cases

  • End-to-end PR update triggered by Jira ticket state
  • Attach visual documentation and screenshots to PR descriptions
  • Resume from intermediate steps using a stateful workflow engine
  • Support rework cycles via --force to refresh PR content after changes

Quick Start

Run the /work-pr <ticket-id> [--force] command to update the PR description and attach visuals.

Frequently Asked Questions about work-pr

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

FAQPage Schema
How do I automatically update a PR description from a Jira ticket?▼

You can automatically update a PR description from a Jira ticket by triggering the workflow with a ticket ID. This automation reduces manual toil by applying current implementation details directly to the pull request.

How do I attach visual documentation to a pull request linked to Jira?▼

You can attach visual documentation to a pull request by running the automated workflow with your Jira ticket ID. This process adds screenshots and visual artifacts directly to the PR description to keep stakeholders aligned.

Can I refresh PR content after rework cycles using a stateful workflow engine?▼

Yes, you can refresh PR content after rework cycles by forcing the workflow to rerun. The stateful workflow engine uses SHA-based caching and state tracking to resume from intermediate steps and update the description.

Do I need a workflow engine to automate PR updates for Jira tasks?▼

Yes, a workflow engine is required to automate PR updates for Jira tasks. It enables state tracking and SHA-based caching, which are necessary for supporting intermediate step resumes and multi-ticket orchestration within a single workflow.

What is the best way to orchestrate multi-ticket PR updates in a single workflow?▼

The best way to orchestrate multi-ticket PR updates is using a stateful workflow engine triggered by Jira ticket state. This approach handles end-to-end PR preparation and attaches visual documentation across multiple tickets within a single workflow.

Why does updating PR descriptions manually create alignment issues for Jira tasks?▼

Updating PR descriptions manually creates alignment issues because it introduces toil and delays updating implementation details. Automating this process keeps stakeholders aligned with the current state of the Jira-tied tasks.

Related Skills

Explore More Software Engineering Skills→
Hamad-CenterHamad-Center
3

drift-start

Record git commit SHA and branch with ticket info in `.drift/config.json`.

Official
Intermediate
CodySwannGTCodySwannGT
3

jira-sync

Synchronize plan progress and development milestones to linked JIRA tickets.

Community
Intermediate
ybbms777ybbms777
1

feature-video

Record browser interactions and embed MP4 walkthrough videos in GitHub pull request descriptions.

Community
Advanced
Progery222Progery222

github-workflow-automation

Automate GitHub repository management, CI/CD pipelines, and pull request workflows.

Community
Advanced