skills.rest
mintuz
mintuzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pseudocode

Renders module boundaries, types, signatures, and cited call graphs as pseudocode.

3|Updated Nov 8, 2014
Search Tags:#code analysis#module boundaries#pseudocode#call graph#execution flow#code planning#signatures
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill pseudocode-mintuz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pseudocode
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/pseudocode
Command: npx skills add https://github.com/mintuz/.dotfiles --skill pseudocode-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how code composes—its module boundaries, types, signatures, and execution flow—requires reading many files and mentally tracing calls, which is slow and error-prone for both existing code and planned changes. ## Core Features & Use Cases - Shape Rendering: Collapses code below the waterline to intent while preserving every name, type, and path with file-and-line citations from the source. - Cited Call Graphs: Produces one indented call graph per wiring (production, tests, feature flags), annotating conditional, async, error, boundary, and unresolved edges. - Planned Change Support: Renders [NEW] modules, types, and signatures derived from a requirement alongside the existing code they attach to. - Use Case: Before implementing a new checkout endpoint, ask for a pseudocode render of the existing checkout flow to see exactly which modules, types, and boundary crossings the change will touch. ## Quick Start Render pseudocode of the checkout flow starting from the submitCheckout entry point, including its call graph and boundary crossings.

Frequently Asked Questions about pseudocode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate pseudocode from existing source code?▼

Name the entry points to trace from and the frame edge of packages and libraries treated as outside. The render follows every call, records each function's signature with file and line, and collapses bodies to one-line intent statements.

How to visualize a call graph with citations before writing code?▼

Request a render of the planned change marked [NEW] alongside the existing modules it attaches to. The output includes one indented call graph per wiring, with edges annotated for conditions, async calls, errors, and boundary crossings.

Can pseudocode rendering handle unresolved dynamic dispatch?▼

Yes, calls through registries, tables, or interfaces that evidence cannot resolve are recorded as unresolved. The render names the specific binding, registration, or configuration call that would resolve the target.

Does the pseudocode skill modify or review my code?▼

No, the render is read-only and carries no review verdict, diagram, or implementation. It returns the shape of the code as the deliverable and leaves edits and reviews to the workflows that own them.

What are the limitations of waterline-based pseudocode rendering?▼

Pure local computation and private helpers contained inside a module are collapsed to intent, so internal algorithm detail is lost. Paths also end at the frame edge, meaning external library internals are named but not expanded.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
2.9k

wiki-researcher

Trace code paths across multi-file architectures with file and line citations.

Official
Advanced
citypaulcitypaul
723

render-code-shape

Render module boundaries, signatures, and cited call graphs from existing source code.

Community
Intermediate
NovaAI-innovationNovaAI-innovation

test-coverage-improver

Analyze coverage.xml reports and propose high-impact tests for uncovered lines.

Community
Intermediate
ComposioHQComposioHQ
1.9k

perf-profiler

Profiles CPU and memory hotspots in applications and outputs flame graphs and traces.

Official
Advanced