Verified:GitHub

status-report

Fetch GitHub and GitLab activity and generate a JSON status report.

1|Updated Feb 18, 2026

Search Tags:#automation #github #reporting #gitlab #activity #status-report #weekly

One-click install

npx skills add https://github.com/fhrbata/idf-tools-cursor-skills --skill status-report-fhrbata

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: status-report
Source: https://github.com/fhrbata/idf-tools-cursor-skills/tree/main/skills/status-report
Command: npx skills add https://github.com/fhrbata/idf-tools-cursor-skills --skill status-report-fhrbata

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Aggregates GitHub and GitLab activity into a single, reproducible weekly status report, reducing manual data collection and reporting effort.

Core Features & Use Cases

Collects activity events from GitHub and GitLab within a configurable look-back window.
Combines data into a unified structure for reporting and auditing.
Flexible deployment: run against a specific project or globally with a chosen config.

Quick Start

Run the status-report script to fetch GitHub and GitLab activity for the configured look-back period and generate the output file.

Frequently Asked Questions about status-report

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

FAQPage Schema

How do I automate weekly status reports from GitHub and GitLab activity?▼

To automate weekly status reports from GitHub and GitLab activity, you can use a script that fetches and aggregates PRs, commits, issues, and events into a single JSON output. It requires API access credentials and a local config to define the look-back period.

What is the best way to aggregate GitHub and GitLab commits into one report?▼

Aggregating GitHub and GitLab commits into one report is done by fetching activity events from both platforms within a configurable look-back window. The collected data is combined into a unified JSON structure, providing a reproducible weekly summary for reporting and auditing.

Does generating a combined GitLab and GitHub report require API access credentials?▼

Yes, generating a combined GitLab and GitHub report requires API access credentials for both platforms. You also need a local or project-scoped configuration file to specify the target projects and the desired look-back period for fetching the activity data.

Can I configure the look-back period for fetching GitHub and GitLab events?▼

Yes, you can configure the look-back period for fetching GitHub and GitLab events. The script uses a local or project-scoped config file that allows you to define the specific time window, ensuring the generated status report covers the exact weekly timeframe needed.

What format is the output generated when combining GitHub and GitLab activity?▼

The output format generated when combining GitHub and GitLab activity is a JSON file. The script processes the configured look-back period data, aggregates the fetched PRs, commits, issues, and events, and produces this single unified JSON structure for reporting.