Generate a dated markdown repository health report from GitHub CLI data.
npx skills add https://github.com/Abhilash-003/mstack --skill health-abhilash-003
Please help me install this Agent Skill. Skill: health Source: https://github.com/Abhilash-003/mstack/tree/main/health Command: npx skills add https://github.com/Abhilash-003/mstack --skill health-abhilash-003
The health skill reduces the time spent guessing what’s wrong in a repository by producing a single, dated report that highlights stale work, review/CI bottlenecks, dependency alert severity, and recent community activity.
.mstack/reports/{DATE}-health.md and presents prioritized action items without modifying GitHub resources.Run the health skill for your configured repository by saying: "run a health check on this repo".
High-intent search queries and answers about installing and using this skill.
To generate a repo health report, run the health skill against your configured repository. It analyzes stale issues, PR bottlenecks, CI failure rates, and Dependabot alerts, then writes a dated markdown report to .mstack/reports/ for maintenance triage.
A GitHub repo health analysis includes stale issue detection, unlabeled and unassigned issue tracking, PR merge conflict flags, failing CI workflows, abandoned drafts, Dependabot alert severity, and 30-day community activity metrics like commit and contributor momentum.
Yes, you need GitHub CLI (gh) access to monitor CI failure rates and stale pull requests. The health skill reads repository configuration from .mstack/config.yml and requires gh access to extract operational risk signals across issues, PRs, and workflows.
CI flakiness detection works by computing CI failure rates from recent GitHub Actions workflow runs. The health skill flags flaky workflows and identifies failing CI runs within the generated report, allowing maintainers to prioritize unstable pipelines during triage.
You cannot track Dependabot alert severity if dependency scanning is inaccessible, but the health skill degrades gracefully. It skips Dependabot alert summaries and continues generating the operational risk report using available data from issues, PRs, and CI workflows.
The best way to prioritize stale issues and abandoned draft PRs is to generate a consolidated health report that surfaces review bottlenecks and age buckets. The report provides action-ready items without modifying GitHub resources, enabling efficient maintenance triage.
Abhilash-003Generate .mstack/config.yml from detected GitHub repository conventions and labels.
nexus-substrateReconcile technique registries, sync documentation, and audit GitHub issue hygiene.
qvidal01Scan project dependency trees for known security vulnerabilities and report findings.
bytedanceAnalyze GitHub repositories through API calls, web searches, and content fetching.