release-tracker

Compute release umbrella status from linked development issues in GitHub.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill release-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-tracker
Source: https://github.com/ctxr-dev/agent-staff-engineer/tree/main/skills/release-tracker
Command: npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill release-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically derives the status of release umbrellas from linked development issues and ensures the umbrella's Linked Dev Issues count stays accurate.

Core Features & Use Cases

  • Computes umbrella.Status from all linked issues for a release tracker project.
  • Keeps the umbrella body blocks up to date with current linked issues and statuses.
  • Enforces depth/read-only guardrails to prevent unintended changes.

Quick Start

Run the release-tracker reconciliation to recompute umbrella statuses from linked issues.

Frequently Asked Questions about release-tracker

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

FAQPage Schema
How do I automatically sync GitHub release umbrella statuses with linked development issues?

You can sync GitHub release umbrella statuses by recomputing the umbrella status from all linked development issues. The tracker updates umbrella fields and the Linked Dev Issues section whenever dev-issue updates or linking changes occur.

What is a release umbrella and how does it track linked issues on GitHub?

A release umbrella aggregates development issues across GitHub projects to derive a unified release status. It tracks linked issues by continuously recomputing status and updating the Linked Dev Issues count and body blocks within the umbrella.

How do I recompute release tracker umbrella fields after updating linked issues?

To recompute release umbrella fields after updating linked issues, trigger a reconciliation process that recalculates the status from all linked issues. It applies idempotent writes to update the Linked Dev Issues section and status fields accurately.

Can I use release tracking automation across multiple GitHub projects?

Yes, release tracking automation applies to GitHub-based release umbrellas across multiple projects. It recomputes umbrella statuses from linked development issues and ensures consistent tracking regardless of project boundaries within the tracker scope.

What are the limitations or guardrails when updating a GitHub release umbrella?

Updating a GitHub release umbrella is constrained by depth and read-only guardrails defined in trackers.release. These guardrails prevent unintended changes by enforcing strict limits on field modifications and ensuring idempotent writes to umbrella blocks.