skills.rest
gestaosian
gestaosianOFFICIAL
Explore all skills by this author →
GitHub

gtsi-status-report

Generates structured period status reports from git log, pull requests, tasks, and saved contexts.

Updated May 21, 2026
Search Tags:#markdown#github#reporting#status report#Sprint report#git log#weekly summary
One-click install
npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-status-report-gestaosian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtsi-status-report
Source: https://github.com/gestaosian/gtsi-claude-skills/tree/main/plugins/gtsi-ops-plugin/skills/gtsi-status-report
Command: npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-status-report-gestaosian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Compiling a weekly or sprint status report manually means digging through git history, pull requests, and task lists, then formatting everything for leadership. This Skill automates that consolidation and produces a structured, reviewable report saved per author. ## Core Features & Use Cases - Multi-source data gathering: Collects the author's git log, GitHub PRs via gh, saved contexts in .gtsi/context/, and completed tasks for the chosen period. - Structured report format: Produces a Markdown report with sections for deliveries, work in progress, blockers, risks, next steps, and support requests, using icons for quick scanning. - Human review before saving: Always presents a draft in the conversation for user edits before writing to .gtsi/reports/<author-slug>/. - Use Case: Before a Monday leadership meeting, ask for the week's status report; the Skill gathers your merged PRs, commits, and completed tasks, drafts the summary, and saves it after your approval. ## Quick Start Ask the assistant to generate your status report for the last week and review the draft before it is saved.

Frequently Asked Questions about gtsi-status-report

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

FAQPage Schema
How do I generate a weekly status report from git history?▼

Request a status report and the Skill runs git log filtered by your author email over the chosen period, combines it with PRs and completed tasks, then drafts a structured summary. You review the draft before it is saved to .gtsi/reports/.

What data sources does a status report generator use?▼

This Skill uses four sources: the author's git log without merges, GitHub PRs listed via the gh CLI, saved contexts in .gtsi/context/<author>/, and completed tasks from the task list. Missing sources are reported as none rather than invented.

Can I generate a report for a sprint or month instead of a week?▼

Yes, the default period is the last week, but the Skill accepts alternatives like last fortnight, current sprint, or month. It confirms the period with you before collecting data.

Does the status report get saved automatically without review?▼

No, the Skill always presents a draft in the conversation first and only writes the file after your adjustments and approval. It also avoids including confidential information without confirmation.

Where are generated status reports stored?▼

Reports are saved as Markdown files under .gtsi/reports/<author-slug>/, named with the date and ISO week number, such as 2026-06-05-semana-23.md. The author slug is derived from the git user name.

Related Skills

Explore More Product & Management Skills→
cloudofgeorgecloudofgeorge

context-save

Save git state, decisions, and remaining tasks for session resumption.

Community
Intermediate
Negentropy-LabyNegentropy-Laby
3

retrospective

Analyze sprint data to generate a structured retrospective markdown report.

Official
Advanced
HexalithHexalith

bmad-review

Reviews diffs, pull requests, and documents through configurable lenses and reports triaged findings.

Official
Advanced
PayRamPayRam
155

payram-analytics

Query PayRam analytics via MCP tools for payments, user growth, and transaction summaries.

Official
Intermediate