status-reporting

Generic pattern for generating comprehensive status reports by gathering data from version control, code review platforms, issue trackers, and CI/CD systems, then aggregating and presenting in scannable format. Use when checking project status, starting sessions, reviewing activity, or when status report, sitrep, project overview, or what's changed are mentioned. Supports natural language time constraints and stack-aware organization.

⭐4stars🔀0forks📁View on GitHub🕐Updated Dec 31, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill automates the generation of comprehensive project status reports by aggregating real-time data from version control systems (VCS), code review platforms, issue trackers, and CI/CD pipelines. It provides a scannable 'sitrep' that highlights recent activity, PR relationships, and critical blockers, helping developers and managers maintain project momentum without manual data collection.

Use Cases

  • Daily Standups: Quickly generate a summary of the last 24 hours of activity across Git, GitHub, and Jira to streamline team synchronization.
  • Session Context Refresh: Use the 'sitrep' command when starting a new work session to understand recent commits and PR status changes since your last login.
  • Blocker Identification: Automatically detect and highlight failed CI/CD runs, pending code reviews, or high-priority issues that are stalling project progress.
  • Stack-Aware Review: Visualize complex branch hierarchies and PR dependencies to understand the impact of changes across a multi-layered development stack.
  • Stakeholder Reporting: Create high-level project overviews including recent milestones and current deployment status for non-technical stakeholders.
namestatus-reporting
version1.0.0
descriptionThis skill should be used when checking project status, starting sessions, reviewing activity, or when "sitrep", "status report", or "what's changed" are mentioned.

Status Reporting

Gather -> aggregate -> present pattern for comprehensive project status across VCS, PRs, issues, CI.

  • Starting work sessions (context refresh)
  • Checking project/team activity
  • Understanding PR/stack relationships
  • Quick status overview before planning
  • Reviewing recent changes across systems
  • Understanding blockers

NOT for: deep-dive into specific items, real-time monitoring, single-source queries

Three-phase workflow:

  1. Gather - collect from multiple sources
  2. Aggregate - combine, filter, cross-reference by time/stack/status
  3. Present - format for scanning with actionable insights

Key principles:

  • Multi-source integration (VCS + code review + issues + CI)
  • Time-aware filtering (natural language -> query params)
  • Stack-aware organization (group by branch hierarchy)
  • Scannable output (visual indicators, relative times)
  • Actionable insights (highlight blockers, failures)

Phase 1: Parse Constraints

Extract time from natural language:

  • "last X hours" -> -Xh
  • "past X days" / "last X days" -> -Xd
  • "yesterday" -> -1d
  • "this morning" / "today" -> -12h
  • "this week" -> -7d
  • "since {date}" -> calculate days back

Default: 7 days if unspecified.

Phase 2: Gather Data

Run parallel queries for each available source:

  1. VCS State - branch/stack structure, recent commits, working dir status
  2. Code Review - open PRs, CI status, review decisions, activity
  3. Issues - recently updated, status, priority, assignments
  4. CI/CD - pipeline runs, success/failure, error summaries

Skip unavailable sources gracefully.

Phase 3: Aggregate

Cross-reference and organize:

  • Group PRs by stack position (if stack-aware)
  • Filter all by time constraint
  • Correlate issues with PRs/branches
  • Identify blockers (failed CI, blocking reviews)
  • Calculate relative timestamps

Phase 4: Present

Format for scanning:

  • Hierarchical sections (VCS -> PRs -> Issues -> CI)
  • Visual indicators (✓ ✗ ⏳ for status)
  • Relative timestamps for recency
  • Highlight attention-needed items
  • Include links for deep-dive

See templates.md for section formats.

VCS - stack visualization, commit history, working dir state

  • Stack-aware (Graphite, git-stack): hierarchical branch relationships
  • Standard git: branch, log, remote tracking

Code Review - PRs/MRs, CI checks, reviews, comments

  • Platforms: GitHub, GitLab, Bitbucket, Gerrit

Issues - recent updates, metadata, repo relationships

  • Platforms: Linear, Jira, GitHub Issues, GitLab Issues

CI/CD - runs, success/failure, timing, errors

  • Platforms: GitHub Actions, GitLab CI, CircleCI, Jenkins

Tool-specific: graphite.md, github.md, linear.md, beads.md

Cross-Referencing:

  1. PRs to branches (by name)
  2. Issues to PRs (by ID in title/body)
  3. CI runs to PRs (by number/SHA)
  4. Issues to repos (by reference)

Stack-Aware Organization:

  • Group PRs by hierarchy
  • Show parent/child relationships
  • Indicate current position
  • Highlight blockers in stack order

Filtering:

  • Time: apply to all sources, use most recent update
  • Status: prioritize action-needed, open before closed

Relative Timestamps:

  • < 1 hour: "X minutes ago"
  • < 24 hours: "X hours ago"
  • < 7 days: "X days ago"
  • = 7 days: "X weeks ago" or absolute

Visual Indicators:

  • ✓ success | ✗ failure | ⏳ pending | ⏸ draft | 🔴 blocker
  • ▓▓▓░░ progress (3/5)
  • ◇ minor | ◆ moderate | ◆◆ severe

Output Structure:

=== STATUS REPORT: {repo} ===
Generated: {timestamp}
{Time filter if applicable}

{VCS_SECTION}
{PR_SECTION}
{ISSUE_SECTION}
{CI_SECTION}

⚠️ ATTENTION NEEDED
{blockers and action items}

See templates.md for detailed section templates.

Use scripts/sitrep.ts for automated gathering:

./scripts/sitrep.ts              # All sources, 24h default
./scripts/sitrep.ts -t 7d        # Last 7 days
./scripts/sitrep.ts -s github    # Specific sources
./scripts/sitrep.ts --format=text

Outputs JSON (structured) or text (human-readable). Reduces agent tool calls 80%+.

See implementation.md for script structure and patterns.

Required: VCS tool (git, gt, jj), shell access

Optional (graceful degradation):

  • Code review CLI (gh, glab)
  • Issue tracker MCP/API
  • CI/CD platform API

Works with ANY available subset.

ALWAYS:

  • Parse time constraints before queries
  • Execute queries in parallel
  • Handle missing sources gracefully
  • Use relative timestamps
  • Highlight actionable items
  • Provide links for deep-dive
  • Format for scanning

NEVER:

  • Fail entirely if one source unavailable
  • Block on slow queries (use timeouts)
  • Expose credentials
  • Dump raw data without organization

As session starter:

  1. Generate report (understand state)
  2. Identify attention-needed items
  3. Plan work (prioritize by blockers)
  4. Return periodically (track progress)

Cross-skill references:

  • Failing CI -> debugging-and-diagnosis
  • Before planning -> use report for context
  • When blocked -> check dependencies

Automation: daily standup, pre-commit hooks, PR creation context

Tool integrations:

Implementation:

Examples:

Formatting: