This skill should be used when checking project status, starting sessions, reviewing activity, or when sitrep, status report, or what's changed are mentioned.
Generates comprehensive project status reports by aggregating data from VCS, PRs, issues, and CI/CD systems.
npx claudepluginhub outfitter-dev/outfitterThis skill inherits all available tools. When active, it can use any tool Claude has access to.
EXAMPLES.mdreferences/beads.mdreferences/github.mdreferences/graphite.mdreferences/implementation.mdreferences/linear.mdreferences/templates.mdscripts/detect.tsscripts/gatherers/beads-gatherer.tsscripts/gatherers/github-gatherer.tsscripts/gatherers/graphite-gatherer.tsscripts/gatherers/linear-gatherer.tsscripts/lib/time.tsscripts/lib/types.tsscripts/sitrep.tsGather -> aggregate -> present pattern for comprehensive project status across VCS, PRs, issues, CI.
<when_to_use>
NOT for: deep-dive into specific items, real-time monitoring, single-source queries
</when_to_use>
<core_pattern>
Three-stage workflow:
Key principles:
</core_pattern>
<workflow>Stage 1: Parse Constraints
Extract time from natural language:
-Xh-Xd-1d-12h-7dDefault: 7 days if unspecified.
Stage 2: Gather Data
Run parallel queries for each available source:
Skip unavailable sources gracefully.
Stage 3: Aggregate
Cross-reference and organize:
Stage 4: Present
Format for scanning:
✓ ✗ ⏳ for status)See templates.md for section formats.
</workflow><data_sources>
VCS - stack visualization, commit history, working dir state
Code Review - PRs/MRs, CI checks, reviews, comments
Issues - recent updates, metadata, repo relationships
CI/CD - runs, success/failure, timing, errors
Tool-specific: graphite.md, github.md, linear.md, beads.md
</data_sources>
<aggregation>Cross-Referencing:
Stack-Aware Organization:
Filtering:
Relative Timestamps:
= 7 days: "X weeks ago" or absolute
Visual Indicators:
✓ success | ✗ failure | ⏳ pending | ⏸ draft | 🔴 blocker▓▓▓░░ progress (3/5)◇ minor | ◆ moderate | ◈ severeOutput 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.
</presentation> <scripts>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.
</scripts> <dependencies>Required: VCS tool (git, gt, jj), shell access
Optional (graceful degradation):
Works with ANY available subset.
</dependencies> <rules>ALWAYS:
NEVER:
As session starter:
Cross-skill references:
Automation: daily standup, pre-commit hooks, PR creation context
</integration> <references>Tool integrations:
Implementation:
Examples:
Formatting:
</references>Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.