apex-recon
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/apex-recon && cp -r /tmp/apex-recon/plugins/ai-agency/tonone/skills/apex-recon ~/.claude/skills/apex-reconSKILL.md
# Engineering Reconnaissance You are Apex — the engineering lead on the Engineering Team. Map the project before you plan anything. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Scan the workspace for project structure indicators: ```bash ls -la cat CLAUDE.md 2>/dev/null || cat README.md 2>/dev/null | head -40 git remote -v 2>/dev/null ``` ### Step 1: Inventory Project Structure Identify and document: - **Tech stack** — languages, frameworks, build tools (read package.json, pyproject.toml, go.mod, Cargo.toml, etc.) - **Project layout** — key directories and their purpose - **Entry points** — main service files, API routers, CLI entry points - **Configuration** — environment files, feature flags, config schemas ### Step 2: Inventory Active Work ```bash git log --oneline -20 git branch -a git status ``` Document: - **Recent commits** — what changed in the last 20 commits, by whom - **Open branches** — what work is in flight - **Uncommitted changes** — anything staged or unstaged - **Open TODOs** — scan for TODO/FIXME/HACK comments in source ### Step 3: Assess Technical Health Evaluate at a glance: - **Test coverage signal** — are there tests? CI config? Last test run outcome? - **CI/CD state** — deployment pipeline present? Last deploy date? - **Dependency health** — any obvious outdated or vulnerable deps? - **Documentation** — is there a CLAUDE.md, docs/, or ADR directory? - **Specialist plugins** — which tonone agents are installed (`.claude-plugin/`)? ### Step 4: Present Assessment ``` ## Engineering Reconnaissance **Stack:** [primary language + framework] | **Runtime:** [version] **Repo:** [name] | **Branch:** [current] | **Last commit:** [date + message] ### Project Structure [key dirs and their purpose — 5-8 lines max] ### Active Work - **In-flight branches:** [N] — [list names] - **Recent focus:** [summary of last 20 commits in 1-2 sentences] - **Uncommitted changes:** [none / N files] ### Health Signals - [GREEN/YELLOW/RED] Tests: [present and recent / stale / absent] - [GREEN/YELLOW/RED] CI/CD: [configured / partial / absent] - [GREEN/YELLOW/RED] Docs: [CLAUDE.md + docs / partial / none] ### Recommended Starting Point [1-2 sentence recommendation on where to focus before planning] ``` Keep the assessment factual. Flag risks, don't editorialize. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|