skills.rest
bostonaholic
bostonaholicCOMMUNITY
Explore all skills by this author →
Website𝕏@bostonaholicGitHub

tracking-tickets

Synchronize pull request statuses with external issue trackers and manage ticket transitions.

8|1|Updated Mar 28, 2026
Search Tags:#automation#workflow#devops#github#issue-tracking#pull-request
One-click install
npx skills add https://github.com/bostonaholic/team --skill tracking-tickets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tracking-tickets
Source: https://github.com/bostonaholic/team/tree/main/skills/tracking-tickets
Command: npx skills add https://github.com/bostonaholic/team --skill tracking-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates manual ticket management overhead by ensuring that pull requests and issue trackers remain perfectly synchronized throughout the development lifecycle.

Core Features & Use Cases

  • Automated State Transitions: Automatically moves tickets to in-progress or in-review based on PR status.
  • Intelligent PR Linking: Automatically appends closing footers to PRs to ensure tickets are resolved upon merge.
  • Multi-repo Support: Handles complex multi-repository workflows by distinguishing between home and companion PRs to prevent premature ticket closure.

Quick Start

Ask the team to link the current pull request to the ticket identified in the task metadata.

Frequently Asked Questions about tracking-tickets

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

FAQPage Schema
How do I automate issue tracking status updates from pull requests?▼

Automated ticket lifecycle synchronization moves issue tracker statuses based on pull request states. It transitions tickets to in-progress or in-review when PRs open, eliminating manual status updates across development platforms.

How do I automatically close issue tracker tickets when a pull request is merged?▼

Intelligent PR linking appends closing footers to pull requests so issue trackers automatically resolve linked tickets upon merge. This ensures accurate ticket resolution without manual intervention across the development lifecycle.

Can I synchronize ticket status across multi-repo environments with companion pull requests?▼

Multi-repo workflow support distinguishes between home and companion pull requests to prevent premature ticket closure. It ensures accurate ticket resolution by verifying the correct repository context before transitioning issue statuses.

What is the best way to link a pull request to an issue tracker ticket?▼

The best way to link a pull request is to reference the ticket identified in the task metadata. The automation logic then detects this link and appends the necessary closing footers for synchronization.

Why does my ticket close prematurely when a companion pull request merges?▼

Tickets close prematurely when automation fails to distinguish home PRs from companion PRs. This skill prevents premature closure by verifying repository context before transitioning the ticket resolution state.

Related Skills

Explore More Software Engineering Skills→
twjarviszyra-webtwjarviszyra-web
3

github-auth

Configure GitHub authentication for git and gh workflows.

Community
Intermediate
chrislyonschrislyons

git.release.prep

Automates release prep with semantic versioning, changelog generation, and GitHub publishing.

Community
Intermediate
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
SharpAISharpAI
3.0k

webhook-trigger

Forward Aegis events to webhook URLs with custom headers and filtering.

Official
Intermediate