ghreport

Generates a read-only GitHub repository status report with CI and security data.

30|5|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/bjcoombs/ai-native-toolkit --skill ghreport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghreport
Source: https://github.com/bjcoombs/ai-native-toolkit/tree/main/skills/ghreport
Command: npx skills add https://github.com/bjcoombs/ai-native-toolkit --skill ghreport

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill solves the visibility gap in large GitHub organizations by providing a consolidated, read-only report on repository health, security posture, and CI status without requiring manual inspection of every individual repository.

Core Features & Use Cases

  • Org-Wide Health Monitoring: Aggregates open PR counts, CI status, and security alert data across all repositories in an organization.
  • Security & Compliance Auditing: Identifies unprotected default branches and tracks Dependabot, code-scanning, and secret-scanning alerts.
  • Use Case: A team lead can use this to quickly identify which repositories have failing CI pipelines or open security vulnerabilities that require immediate developer attention.

Quick Start

Run the ghreport skill from your organization root directory to generate a summary of all repository states and save the detailed report to a markdown file.

Frequently Asked Questions about ghreport

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

FAQPage Schema
How do I generate a health and security report for all repositories in a GitHub organization?

To generate a GitHub organization health report, you can use a tool that aggregates open pull requests, CI workflow outcomes, security alert counts, and branch protection settings across all repositories into a consolidated read-only markdown summary.

Can I audit branch protection and Dependabot alerts across multiple GitHub repositories at once?

Yes, you can audit branch protection and Dependabot alerts across multiple GitHub repositories by aggregating remote API data, tracking code-scanning and secret-scanning alerts, and identifying unprotected default branches in a single report.

Do I need the GitHub CLI and jq installed to monitor CI workflow outcomes and security posture?

Yes, you need the GitHub CLI for local authentication and the jq utility to process and aggregate remote API data when monitoring CI workflow outcomes and security posture across an organization's repository set.

What is the best way to identify failing CI pipelines and open security vulnerabilities in large GitHub organizations?

The best way to identify failing CI pipelines and open security vulnerabilities in large GitHub organizations is to generate a comprehensive status report that analyzes CI workflow outcomes and aggregates security alert counts without requiring manual inspection of every individual repository.

Does this repository health monitoring approach modify any GitHub settings or workflows?

No, this repository health monitoring approach is strictly read-only. It aggregates data on pull requests, CI status, and security alerts to provide a consolidated snapshot without modifying any GitHub settings, workflows, or repository configurations.

What limitations exist when tracking code-scanning and secret-scanning alerts across personal accounts versus organizations?

The tool generates a comprehensive status report for repositories within a GitHub organization or personal account. It requires local authentication via the GitHub CLI to successfully process and aggregate remote API data for both account types.