issue-pr-deploy-traceability

Detect missing traceability from GitHub Issues to PRs to Deploy/Releases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill issue-pr-deploy-traceability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-pr-deploy-traceability
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/scheduled-tasks/issue-pr-deploy-traceability
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill issue-pr-deploy-traceability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of broken traceability between Issues, their implementing PRs, and the resulting Deploy/Releases, so you can quickly answer “where did that change go?”

Core Features & Use Cases

  • Detect merged PRs that never produced a deploy/release tag: flags potentially undeployed merges by checking for release tags created near the merge time.
  • Find open issues that appear stalled without implementation: identifies issues older than 14 days that are not referenced by any PR and aren’t explicitly skipped by risk-appropriate labels.
  • Surface PRs that don’t reference an Issue: finds merged PRs that lack closes/fixes/refs linkage patterns or open PRs whose bodies don’t include the expected issue reference.

Use case: run it every Saturday 6am to audit the repo’s hygiene and ensure every “Fixes/Closes #N” ends up in a corresponding deployed/released change.

Quick Start

Run the repository audit named issue-pr-deploy-traceability and then follow its outputs to append the weekly traceability report to the configured Notion page while sending the one-line Pushover summary and escalation flags when thresholds are exceeded.

Frequently Asked Questions about issue-pr-deploy-traceability

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

FAQPage Schema
How do I track merged pull requests that never produced a deploy or release tag?

To find orphaned pull requests, audit PR bodies for missing closes, fixes, or refs linkage patterns. This traceability check surfaces both merged and open PRs that lack proper issue references, helping maintain clear repository hygiene.

What is the best way to identify stalled GitHub issues with no implementation?

Issue tracking audits identify stalled issues older than 14 days that are not referenced by any PR. This repository hygiene process excludes issues with risk-appropriate skip labels, isolating those genuinely lacking implementation progress.

How do I automate a weekly release audit for GitHub issues and pull requests?

Yes, you can append weekly traceability reports to Notion and send Pushover summaries. After the release audit runs, it outputs structured reporting and escalation flags when thresholds are exceeded, enabling automated notification workflows.

Does this traceability audit require the GitHub CLI to list pull requests and issues?

Yes, the audit requires the GitHub CLI to list and cross-reference pull requests, issue numbers, and release tags. This gh-based approach enables accurate detection of orphaned PRs and undeployed merges across 7 to 14 day time windows.