Skip to main content
skill CX Codex

status-report-generator — Claude Code skill: reports and setup

The status-report-generator Claude Code skill builds project status reports from Git activity, task context, and milestone tracking. It can create weekly updates, sprint reviews, and stakeholder reports.

MIT 145 installs ★ 114 updated 2026-11-10

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill status-report-generator -a claude-code
Open on GitHub

What status-report-generator does

The skill gathers project activity and turns it into a status report. Sections can cover completed work, active tasks, schedules, blockers, risks, upcoming work, and metrics.

Git data comes from commands such as git log, git shortlog, and git diff; GitHub pull requests and issues can be queried with gh. Jira and Linear data can come from their APIs or CLIs. Reports can be formatted as Markdown, HTML, or PDF. GitHub, Jira, and Linear data require gh or the relevant service API or CLI.

What it helps with

  • summarize a week of Git activity
  • group completed tasks by sprint or milestone
  • surface project blockers and risks
  • prepare a status update for stakeholders
  • format a report as Markdown, HTML, or PDF

Example prompts for the agent

  • Create a weekly project update from Git history and current tasks.
  • Draft a sprint review covering completed work, blockers, and the next period.
  • Prepare a stakeholder report in Markdown with project metrics.

How to install status-report-generator

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill status-report-generator -a claude-code

2Manually: put the files in place

~/.claude/skills/status-report-generator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/status-report-generator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about status-report-generator

How do I install status-report-generator in Claude Code?

Run npx skills add travisjneuman/.claude --skill status-report-generator -a claude-code. The skill file is at ~/.claude/skills/status-report-generator/SKILL.md.

What does status-report-generator do?

It assembles project status reports from Git activity, task systems, and milestone tracking. Reports can cover progress, risks, blockers, upcoming work, and metrics.

What does status-report-generator need to work?

GitHub data requires gh; Jira and Linear data can be retrieved through their APIs or CLIs. Git history can be gathered with git commands.

Source text

SKILL.md · MIT
---
name: status-report-generator
description: Project status report generation from git history, task context, and milestone tracking. Use when creating weekly updates, sprint reviews, stakeholder reports, or project dashboards.
---

# Status Report Generator

Structured frameworks for generating project status reports from code activity, task systems, and milestone tracking.

## Status Report Structure

### Standard Report Sections

```
STATUS REPORT OUTLINE:

1. TL;DR (3-5 bullets)
   - What was accomplished
   - What's in progress
   - What's blocked or at risk
   - Key decision needed (if any)

2. STATUS INDICATOR
   - Overall: GREEN / YELLOW / RED
   - Schedule: on track / at risk / behind
   - Scope: stable / expanding / contracting
   - Budget: on track / at risk / over (if applicable)

3. ACCOMPLISHMENTS (completed this period)
   - Bullet list with links to PRs/tickets
   - Grouped by workstream or milestone
   - Include metrics where possible

4. IN PROGRESS (active work)
   - Current tasks and expected completion
   - Progress indicators (% or status)
   - Owner for each item

5. BLOCKERS AND RISKS
   - Active blockers with escalation status
   - Emerging risks with mitigation plans
   - Dependencies on other teams

6. UPCOMING (next period)
   - Planned work for next sprint/week
   - Key milestones approaching
   - Decisions needed

7. METRICS (if applicable)
   - Velocity / throughput
   - Quality indicators (bugs, incidents)
   - Business metrics impact
```

## Data Extraction Methods

### From Git History

```
GIT DATA FOR STATUS REPORTS:

COMMITS THIS PERIOD:
git log --since="1 week ago" --oneline --no-merges

COMMITS BY AUTHOR:
git shortlog --since="1 week ago" -sn --no-merges

FILES CHANGED:
git diff --stat HEAD~{n}..HEAD

MERGED PRs (GitHub):
gh pr list --state merged --search "merged:>=2025-01-01"

PR SUMMARY:
gh pr list --state merged --json title,author,mergedAt,url \
  --jq '.[] | "- \(.title) (@\(.author.login)) \(.url)"'

OPEN PRs:
gh pr list --state open --json title,author,url \
  --jq '.[] | "- \(.title) (@\(.author.login)) \(.url)"'

RELEASE NOTES:
git log --since="1 week ago" --pretty=format:"- %s" --no-merges \
  | grep -E "^- (feat|fix|refactor|perf):"
```

### From Task Systems

```
TASK DATA EXTRACTION:

JIRA (via API or CLI):
- Tickets moved to "Done" this sprint
- Tickets currently "In Progress"
- Tickets in "Blocked" status
- Story points completed vs planned

GITHUB ISSUES:
gh issue list --state closed --search "closed:>=2025-01-01"
gh issue list --state open --label "in-progress"
gh issue list --state open --label "blocked"

LINEAR (via API):
- Completed issues this cycle
- In-progress issues
- Blocked issues with reason
- Cycle velocity metrics

GENERIC EXTRACTION TEMPLATE:
| Ticket | Title | Status | Owner | Notes |
|--------|-------|--------|-------|-------|
|        |       |        |       |       |
```

### Automated Report Generation

```
REPORT GENERATION SCRIPT APPROACH:

1. PULL DATA
   - Git log for the period
   - PR merge data
   - Issue/ticket status
   - CI/CD metrics (build success rate, deploy count)

2. CATEGORIZE
   - Group commits by type (feat, fix, refactor, etc.)
   - Group issues by milestone or epic
   - Identify blockers from issue labels

3. SUMMARIZE
   - Count: X features shipped, Y bugs fixed, Z PRs merged
   - Highlight: biggest wins and remaining risks
   - Metrics: velocity, cycle time, throughput

4. FORMAT
   - Apply template for audience (exec, team, detailed)
   - Add status indicators (RAG)
   - Include links to source data

OUTPUT FORMATS:
- Markdown (for Slack, GitHub, internal docs)
- HTML (for email)
- PDF (for stakeholder presentations)
```

## Reference files

Detailed material is in separate files so this overview stays short. Read only the file whose topic matches the task; each one is self-contained. Paths are relative to the folder that holds this `SKILL.md` (in the full toolkit install, `~/.claude/skills/status-report-generator/`).

| Topic | File | Covers |
| --- | --- | --- |
| RAG Status Framework | [`references/rag-status-framework.md`](references/rag-status-framework.md) | Status Definitions; RAG Assessment Matrix; Status Change Triggers |
| Stakeholder-Appropriate Detail Levels | [`references/stakeholder-appropriate-detail-levels.md`](references/stakeholder-appropriate-detail-levels.md) | Executive Summary (C-Level / VP); Team Status (Engineering / Product); Detailed Technical Report |
| Sprint Review Template | [`references/sprint-review-template.md`](references/sprint-review-template.md) | 41 lines |
| Milestone Tracking | [`references/milestone-tracking.md`](references/milestone-tracking.md) | Milestone Dashboard Template; Burn-Down Narrative |
| Risk and Blocker Escalation | [`references/risk-and-blocker-escalation.md`](references/risk-and-blocker-escalation.md) | Blocker Escalation Format; Risk Register Template |
| Status Report Quality Checklist | [`references/status-report-quality-checklist.md`](references/status-report-quality-checklist.md) | 15 lines |
| Status Report Anti-Patterns | [`references/status-report-anti-patterns.md`](references/status-report-anti-patterns.md) | 30 lines |

## See Also

- [Codebase Documenter](../codebase-documenter/SKILL.md)
- `anthropic-skills:docx` (Anthropic document skill)
- [Product Management](../product-management/SKILL.md)
- [Finance](../finance/SKILL.md)

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Notes, tasks and projects →

From the same set117

The whole set →
monitoring-observability monitoring-observability equips AI coding agents to set up OpenTelemetry, structured JSON logging, and distributed tracing. Useful when defining SLO alerts or instrumenting services. CX Codex +1 146installs codebase-documenter codebase-documenter turns a repository into readable docs: README, architecture overview, onboarding guide, API reference and code comments. Handy when someone new has to understand the project. CX Codex +1 145installs impact-report-writer The impact-report-writer skill helps structure program impact reports, choose outcome metrics, and plan data visualizations. Use it for annual reports or program evaluations. CX Codex +1 145installs frontend-enhancer frontend-enhancer polishes the visual side of a web app: palette, layout, motion, component states. Useful when the UI still reads as a stock starter. CX Codex +1 145installs generic-ux-designer generic-ux-designer — a UX skill for Claude and other coding agents: design-thinking steps, heuristic review and accessibility checks, packaged as checklists the agent follows. CX Codex +1 145installs performance-engineering performance-engineering — a skill for Claude Code designed for full-stack web application performance optimization. Activates when Core Web Vitals drop, bundle sizes increase, or page response times degrade. CX Codex +1 144installs authentication-patterns authentication-patterns — a Claude Code skill for authentication and authorization patterns. It comes into play when building login flows, MFA, SSO, or access-control models. CX Codex +1 144installs i18n-localization The i18n-localization Claude Code skill guides internationalization and localization work. It activates for translation setup, locale-specific formatting, and adapting an app for multiple regions. CX Codex +1 143installs

Project sponsors

Companies that keep this analytics open