hu-team-staging-status

Generate per-repository staging and development status reports from GitHub and Jira data.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HumandDev/hu-ai-agent-plugin --skill hu-team-staging-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hu-team-staging-status
Source: https://github.com/HumandDev/hu-ai-agent-plugin/tree/main/plugins/humand-product-workflow/skills/hu-team-staging-status
Command: npx skills add https://github.com/HumandDev/hu-ai-agent-plugin --skill hu-team-staging-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clear, up-to-date overview of which code is in staging and which is still in development for a given team, streamlining the release process and improving team visibility.

Core Features & Use Cases

  • Automated Status Reporting: Fetches data from GitHub and Jira to generate a comprehensive status report.
  • Per-Repo Breakdown: Details the status of code across different repositories relevant to the team.
  • Notion Integration: Publishes the generated report to a Notion page for easy access and record-keeping.
  • Use Case: A Product Manager needs to know the exact status of features for the "Raccoon" team before a release. This Skill can generate a report showing which features are in staging, which are in development, and any open PRs, then publish it to Notion.

Quick Start

Generate a staging and develop status report for the "Raccoon" team, using "SQRC" as the Jira project key.

Frequently Asked Questions about hu-team-staging-status

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

FAQPage Schema
How do I generate a staging and development status report for my team across multiple repositories?

You can generate a staging and development status report by fetching GitHub branches and Jira tickets, classifying Pull Requests, and outputting a markdown report. The process integrates with Notion to publish the report and return a page URL.

Can I publish GitHub and Jira staging status directly to a Notion page?

Yes, you can publish staging status directly to a Notion page using the Notion MCP integration. It takes the generated markdown report, creates a Notion page for record-keeping, and returns the page URL.

What's the best way to track which features are in staging versus development before a release?

The best way to track features in staging versus development is to fetch data from GitHub branches and Jira tickets, classify open Pull Requests, and generate a per-repository breakdown. This provides clear release visibility.

Do I need Python and GitHub CLI to track team staging status?

Yes, you need Python 3 and the gh CLI to track team staging status. You also require API access to GitHub and Jira to fetch branch and ticket data for generating the markdown report.

Does this reporting process require a specific Jira project key?

Yes, the reporting process requires a specific Jira project key, such as 'SQRC', to fetch the correct ticket data. This key maps the Jira tickets to the relevant team repositories for the status report.