sync-repo-status

Generate a repository status snapshot of pull requests, branches, issues, and discussions.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill sync-repo-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-repo-status
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/sync-repo-status
Command: npx skills add https://github.com/gittower/git-flow-next --skill sync-repo-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers quickly rebuild a complete, current view of repository activity so they can see what needs attention without manually checking pull requests, branches, issues, and discussions.

Core Features & Use Cases

  • Open Pull Request Triage: Groups PRs by merge readiness and whose move it is, helping identify what can be merged, what needs review, and what is stalled.
  • Branch and Issue Assessment: Reviews local branches without PRs and open issues, highlighting stale work, duplicates, linked PRs, and unanswered reports.
  • Discussion Monitoring: Surfaces unanswered or partially answered discussion threads so maintainers can respond or close the loop.
  • Use Case: A maintainer wants a single operational summary before a release or planning meeting and uses this Skill to generate an updated repository status report.

Quick Start

Use the sync-repo-status skill to regenerate the repository status snapshot and summarize the top maintenance priorities.

Frequently Asked Questions about sync-repo-status

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

FAQPage Schema
How do I get a snapshot of open pull requests and issues for repository triage?

Generate a repository status snapshot to group open pull requests by merge readiness, link issues, and highlight stale branches for triage. This provides a complete current-state view of repository activity so maintainers can see what needs attention.

What's the best way to assess merge readiness for open pull requests?

Assess merge readiness by grouping pull requests by whose move it is and unresolved review states. This identifies what can be merged immediately, what needs review, and what is stalled, creating a prioritized action queue for maintainers.

How do I detect stale branches and unanswered issues in my GitHub repository?

Detect stale branches without PRs and unanswered issues by reviewing local branches and open discussions. This highlights stale work, duplicates, linked PRs, and unanswered reports so maintainers can respond or close the loop.

Do I need GitHub read access to summarize unresolved pull request reviews?

Yes, you need GitHub read access to query repository metadata. This access allows the tool to classify PRs, link issues, and summarize unresolved review and discussion states for a complete repository status report.

Can I monitor unanswered GitHub discussions for open repository threads?

Yes, monitor discussions by surfacing unanswered or partially answered threads. This helps maintainers identify which discussion threads need responses so they can intervene or close the loop during repository triage.

When should I use a repository status report for maintenance prioritization?

Use a repository status report before a release or planning meeting to regenerate the repository status snapshot. This summarizes top maintenance priorities and rebuilds a complete, current view of repository activity for operational planning.