skeleton
Skeleton
Repository context
Make npx --no-install skeleton context "<topic>" the first repository command. Use --path only for a known implementation path and --staged for staged-code questions. Returned document, source, and test excerpts are already read; do not read those files again unless an action requires a complete review. A whole-file excerpt is the entire file. reference lines list every tracked file and line naming an identifier from the request; for a rename or removal, change exactly those lines without searching again. Complete every action line and verify it against the final files. Preserve existing work. If a test is returned, edit and run only that test. Otherwise use one combined command to find and read the focused test. Stop when it passes. Do not run Skeleton audits or validation unless the user requested them, the focused test fails, or you are preparing a pull request (see below). Broader discovery or another context command is reserved for no-context, review gaps, omitted evidence, or a failing focused test.
A packet with review actions or omitted evidence is incomplete. Resolve the relevant gap before relying on active implementation claims. Preserve historical alternatives and future aspirations as qualified intent. A current status means the declared sources are unchanged, not that the document agrees with them; source changes need declared review-deps and source-triggered validation in the consumer.
Source implementation work
For source work, use the returned source excerpt to identify the implementation seam, then locate the nearest focused test with a targeted search. Preserve existing work, make one consistent source/test/document change, then run the focused test after the final edit. Do not replace that final test with a broad audit or an intermediate completion claim.
Do not run Skeleton commands just because Skeleton is installed. They are not a substitute for the focused test.