name	explain-code
description	Produce concise, citation-backed explanations of module behavior, data flow, and important types/APIs.
license	MIT
metadata	{"mode":"read-only","purpose":"explanation"}

Explain Code

When to Use

The user asks "how does X work?" or needs a human-readable overview tied to exact code locations.

Rules

Read-only and source-cited: every non-trivial claim must include path:line.
Keep summaries short and pragmatic. Focus on inputs/outputs, side effects, and error handling.

Output

What it does: 1-4 sentences.
How it works: 3-6 bullets with path:line citations for key statements.
Key types/APIs: short list with path:line.
Edge cases / invariants: 1-3 bullets.

Examples

"Explain handler.Login behavior and where passwords are hashed."
"How does the JWT blacklist work end-to-end?"

Related Skills

file-reader (low-level excerpts), code-navigation (impact mapping)

Más de este repositorio

mismo repositorio

ci-orchestrator

pilinux/gorest

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

2026-06-24502

linter-runner

pilinux/gorest

Execute repository linters and surface highest-priority issues with minimal, targeted fixes.

2026-06-24502

ast-introspection

pilinux/gorest

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

2026-02-19502

build-run

pilinux/gorest

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

2026-02-19502

code-formatter

pilinux/gorest

Apply repository-standard formatting to minimize diff noise and meet linter expectations.

2026-02-19502

code-navigation

pilinux/gorest

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

2026-02-19502

name	explain-code
description	Produce concise, citation-backed explanations of module behavior, data flow, and important types/APIs.
license	MIT
metadata	{"mode":"read-only","purpose":"explanation"}

Explain Code

When to Use

The user asks "how does X work?" or needs a human-readable overview tied to exact code locations.

Rules

Read-only and source-cited: every non-trivial claim must include path:line.
Keep summaries short and pragmatic. Focus on inputs/outputs, side effects, and error handling.

Output

What it does: 1-4 sentences.
How it works: 3-6 bullets with path:line citations for key statements.
Key types/APIs: short list with path:line.
Edge cases / invariants: 1-3 bullets.

Examples

"Explain handler.Login behavior and where passwords are hashed."
"How does the JWT blacklist work end-to-end?"

Related Skills

file-reader (low-level excerpts), code-navigation (impact mapping)