The Monday morning status report is one of those engineering rituals that produces less value than it costs. The lead spends two hours reading Jira, GitHub, and Slack, assembling a narrative for the rest of the team and for stakeholders. The narrative is usually accurate, sometimes slightly behind, and always less informative than reading the underlying data directly. The cost is paid in the lead's time and in the reports that go unread because they describe activity rather than judgment.
A useful status report compresses what the data shows into the questions a stakeholder actually asks: what shipped, what is in progress, what is blocked, what is risky. The data lives in git history, open PRs, recent commits, and the codebase state. The narrative is the editorial layer on top: this branch has been open for 3 weeks (might be stale), this PR has 4 review rounds (signal of architectural friction), this module has churned heavily (worth reviewing for stability). The /apex-status skill produces the editorial report from the underlying data so the lead spends two minutes reviewing rather than two hours assembling.
What a useful status report contains
Four sections. Shipped: what landed in main since the last report, with the headline impact (feature, fix, refactor). In progress: what is open in PRs, with age and review status. Blocked: PRs and branches that have stalled, with the apparent blocker (waiting on review, waiting on dependency, awaiting design decision). Risk: the items that warrant attention even when nothing is broken (long-running branch, high churn module, recent revert).
How /apex-status works
The skill reads git history (commits and merges since the last report), open PRs (with age, review state, comments), recent commit patterns (which areas of the codebase have churned), and any signals from CI (failed builds, slow tests). It produces the four sections in editorial form: what shipped is described by impact, not by commit message; what is in progress is filtered to the items stakeholders care about; what is blocked names the apparent blocker; what is risky names the signal.
The single most useful section is Risk. Stakeholders read shipped and in-progress in many other places; the Risk section is where a status report adds editorial value. /apex-status produces the Risk section from concrete signals (long-open branches, high-churn modules, recent reverts) rather than vague concerns.
Tonone's /apex-status skill produces a CTO-level status report from git history, PRs, and codebase state in minutes rather than hours.
When to use /apex-status
/apex-status is the right call as a weekly Monday-morning report, before a stakeholder review or board update, or when a new lead is taking over and needs to understand the current state. Skip it for daily standups (overkill) or for reports that need detailed sprint metrics (use the team's existing tooling).
| Capability | Tonone | Generalist chatbot | Cursor / Copilot |
|---|---|---|---|
| Reads git history and PRs directly | Yes, no manual assembly | Asks for input | Tool-specific |
| Editorial framing (impact, not commits) | Yes, what shipped means | Commit list | Variable |
| Risk section grounded in signals | Yes, long branches/churn/reverts | Vague concerns | Not in scope |
| Generated in minutes | Yes | Hours | Variable |
Related skills
/apex-status produces the report. For project scoping that precedes execution, /apex-plan is the right call. For takeover of an inherited codebase, /apex-takeover produces the deeper artifact. For cross-cutting code review of a body of work, /apex-review is calibrated to that work.
Install
/apex-status ships with the Apex agent in Tonone for Claude Code. Install Tonone, invoke /apex-status, and the skill produces the status report from the actual repository state.
1. Add to marketplace
2. Install Apex
Frequently asked questions
- What does /apex-status do?
- It reads git history, open PRs, recent commits, and codebase state to produce a CTO-level status report with shipped, in progress, blocked, and risk sections.
- When should I use /apex-status?
- As a weekly Monday-morning report, before a stakeholder review, or when a new lead is taking over.
- How do I install /apex-status?
- Install Tonone for Claude Code via tonone.ai/get-started. /apex-status ships with the Apex agent. Tonone is free and MIT-licensed.