Extract domain-specific terms from a codebase by mining function names, table names, and comments and produce a sorted glossary.
Scans a codebase for recurring domain terms and produces a glossary. Sources include exported function names, database table and column names, and noun phrases inside JSDoc / docstring comments.
repo_dir: project root.lang: dominant language (ts, py, go, java); auto-detected from extension counts otherwise.schema_path: SQL or Prisma schema file to mine for table/column names.find <repo_dir> -name '*.ts' -o -name '*.py' | head -200 | awk -F. '{print $NF}' | sort | uniq -c.rg -oN '\bfunction ([A-Za-z][A-Za-z0-9_]+)' --replace '$1'; Python via rg -oN '\bdef ([a-zA-Z_][a-zA-Z0-9_]+)'; Go via rg -oN 'func \(.*\) ([A-Z][a-zA-Z0-9_]+)\('.getUserById -> [get, user, by, id]. Use a regex split.get, set, is, has, the, to, from, with, for, data, info, value).schema_path, extract CREATE TABLE and column names with rg -oN 'CREATE TABLE\s+(\w+)' -r '$1' and similar for columns./** ... */ and # ... blocks; run a simple POS heuristic — capitalized multi-word phrases inside comments — to find candidate definitions.| Term | Definition | Sample location |.docs/glossary.md.docs/glossary.md with a header note ("Generated from on ") followed by an alphabetical glossary table. Each row's "Sample location" cell links to one file:line where the term appears.
Open three random rows and grep the codebase for the term; the count must be at least the threshold (5). Manually skim ten definitions for sanity — terms whose definitions read as gibberish should be moved to a "needs review" appendix rather than dropped silently. Re-run after changing the stopword list and confirm the glossary changes monotonically (terms only enter or exit, no shuffling).
.gitignore and exclude node_modules, vendor, dist from the scan.usrCt, prdId): supplement with a sibling abbreviations table; do not try to expand.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/glossary-from-codebase.
Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Diff two OpenAPI YAML files and produce a backwards-compatibility changelog grouped into breaking, non-breaking, and additive changes.
Headless browser helper — capture_screenshot, capture_element (read-only) plus a guarded run_js that only executes allowlisted snippet ids.
Read-only RubyGems helper — search_gems, get_gem_info, list_versions. Surface for Ruby dependency discovery from an agent.
Read-only crates.io helper — search_crates, get_crate_info, list_versions. Surface for Rust dependency discovery from an agent.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.