jcosta33/skills

dissect

Trace one unfamiliar or dangerous code path to closure. Use when its callers, flow, state, effects, failures, configuration, tests, or coupling remain unproven. Do not use as the owner of contained work or whole-area inventory.

First seen Jul 13, 2026

Installation

$ npx skills add jcosta33/skills --skill dissect

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jcosta33/skills · top by installs.

npx skills add jcosta33/skills

Browse all from jcosta33/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,819 B
  • docs SUMMARY.md 242 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 36 installs

SKILL.md

Dissect

Trace it to bedrock.

Method

  1. Freeze one question, symbol, workflow, or subsystem and repository state.
  2. Find every entry: API, command, route, event, job, callback, registry, generated binding,

and configuration key.

  1. Trace inbound callers, including dynamic dispatch, string registration, reflection, and generated

call sites.

  1. Trace every branch to terminal effects, including retries, fallbacks, cleanup, cancellation,

error translation, and asynchronous continuation.

  1. Trace data, mutation, persistence, caches, shared state, and external effects.
  2. Trace invalid input, partial state, concurrency, time, exhaustion, dependency failure, and

recovery.

  1. Inspect tests, types, schemas, configuration, documentation, generated files, and runtime wiring.
  2. Close every edge with file:line evidence. Mark every gap Unknown and name missing proof.

Output

Return the report as rendered Markdown.

Question: <one sentence>

State: <stable snapshot>

Flow: <entry -> decisive branches -> terminal effects>

Path:line Proven edge, state, effect, or boundary Unknown

Evidence

For each decisive run, give the command, working directory, state identifier, numeric exit, and the smallest untouched decisive output excerpt. A brief plain-language summary may follow only when the report cannot orient the reader by itself.

Boundaries

Negative claims require the search command and result. Symbol search does not prove reachability. Record exact boundary operators.