ast-introspection

利用Go AST感知分析，枚举符号、提取函数签名，并提出机械安全的重构方案（默认为只读模式）。

SKILL.md

--- frontmatter

name: ast-introspection
description: Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
license: MIT
metadata:
  mode: analysis
  purpose: go-ast

AST Introspection

When to Use

•Need a structure-aware view (functions, methods, types, receivers) or a safe, mechanical refactor proposal that relies on code shape rather than string matches.

What This Skill Does

•Enumerates package-level declarations (funcs, methods, types, const/var) with path:line citations.
•Extracts function/method signatures, receivers, and doc comments.
•Lists imports and flags suspicious patterns (duplicates, likely unused groups).
•Proposes minimal, mechanically-safe refactors (rename, extract, signature change) with verification steps.

Rules

•Prefer read-only inspection (glob, grep, targeted read) before any edit.
•Always include path:line citations for code claims.
•Never perform large automated rewrites without an explicit preview, tests, and verification commands.

Commands

•Enumerate packages: go list ./...
•Quick exported view: go doc <pkg>

Output

•Inventory: compact list of declarations with path:line.
•Findings: 2-8 concise bullets (impact + confidence).
•Proposal: minimal patch plan (files/hunks) + exact verification commands.

Examples

•"List all exported methods on type Auth with file locations."
•"Propose a safe rename for method X and verify callers."

Related Skills

•source-search (broad grep), code-navigation (impact mapping)

References

•llms.txt (project knowledge base)