re-structure-analysis
Analyze codebase structure for reverse engineering. Identify entry points, dependencies, modules, and components with file:line traceability. Creates…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-05 00:16
39,560 results
Analyze codebase structure for reverse engineering. Identify entry points, dependencies, modules, and components with file:line traceability. Creates…
Create a GitHub pull request with a structured summary. TRIGGER when the user asks to commit and push, push changes, open a PR, create a pull request, "ship…
Use for Pstack interface or module design, caller-first sketches, and implementation against a chosen shape.
Use for Pstack code walkthroughs, subsystem behavior, or module placement and ownership questions.
Use for Pstack adversarial review that tries to break a concrete diff or contested design and keeps only findings a run proves.
Use for Pstack comment review, unnecessary narration, or suppressions that conceal code problems.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust…
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is…
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data…
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that…
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of…
Choose migration strategy when an API or schema replaces an old contract: coordinated caller migration and deletion, or staged coexistence for real…
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller…
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states…
Apply when integrating a new requirement into an existing design.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a…
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand…
Use in a Pstack task to show how a system moves between states, such as a product flow, a protocol, or a service, as a Mermaid statechart checked by a TLA+…
Use in a Pstack task to explain both how code works and why it has its shape in plain language.
Use in a Pstack task when writing TypeScript types, validation boundaries, discriminated unions, or public APIs.
Use for Pstack design rationale, regressions, historical constraints, or the evidence behind thresholds.
Drizzle ORM for TypeScript. Covers schema definition, queries, and migrations. Use for type-safe SQL with minimal overhead. USE WHEN: user mentions "drizzle",…