Agent skill · software engineering · jeremylongshore
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
Why this skill is useful
Adds a structured CLI tool for generating CTO-level project status summaries based on git and codebase state, which the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apex Status You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps 1. Check recent commits. 2. Check current work in progress. 3. Read key project files — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them: 4. Synthesize into a CTO-level summary covering: What's shipped (recent completed work) What's in progress (uncommitted changes, active branches) What's blocked (if anything looks stalled or broken) What needs attention next (the obvious next step) 5. Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apex-status