| name | check-status |
| description | This skill should be used when checking project status, starting sessions, reviewing activity, or when sitrep, status report, or what's changed are mentioned. |
| metadata | {"version":"1.0.2"} |
Status Reporting
Gather -> aggregate -> present pattern for comprehensive project status across VCS, PRs, issues, CI.
<when_to_use>
- 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
</when_to_use>
<core_pattern>
Three-stage workflow:
- Gather - collect from multiple sources
- Aggregate - combine, filter, cross-reference by time/stack/status
- 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)
</core_pattern>
Stage 1: Parse Constraints
Extract time from natural language:
