node_modules/get-tsconfig/skills/get-tsconfig/SKILL.md
Find, parse, and query tsconfig.json files — extends resolution, file matching, path alias resolution. Use when reading tsconfig.json, checking if a file belongs to a tsconfig, resolving TypeScript path aliases, or working with tsconfig extends chains.
npx skillsauth add mikeparcewski/wicked-garden get-tsconfigInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Lightweight tsconfig.json parser. No TypeScript dependency. Tested against tsc for correctness.
| Function | Purpose | Returns |
|----------|---------|---------|
| getTsconfig(searchPath?, options?) | Find + parse nearest tsconfig | TsconfigResult \| undefined |
| findTsconfig(searchPath?, options?) | Find nearest tsconfig path only | string \| undefined |
| readTsconfig(path, options?) | Parse tsconfig at known path | TsconfigResult |
| isFileIncluded(tsconfig, filePath) | Check if file is a root file (matches include/exclude/files globs) | boolean |
| resolvePathAlias(tsconfig, specifier) | Resolve compilerOptions.paths alias | string[] |
| getExtendsChain(path, options?) | Get raw extends chain before merging | TsconfigResult<TsconfigJson>[] |
| resolveExtendsChain(chain) | Merge a collected chain (pure, no fs) | TsconfigResult |
type TsconfigResult<Config = TsconfigJsonResolved> = {
path: string
config: Config
}
// TsconfigJson = raw tsconfig shape (includes extends field)
// TsconfigJsonResolved = TsconfigJson without extends (fully merged)
type GetTsconfigOptions = {
configName?: string // default: 'tsconfig.json' (use 'jsconfig.json' for JS projects)
cache?: Map<string, unknown>
includes?: boolean // default: false — when true, validates file is a root file before accepting
}
type ReadTsconfigOptions = {
cache?: Map<string, unknown>
}
import { getTsconfig, isFileIncluded, resolvePathAlias } from 'get-tsconfig'
const tsconfig = getTsconfig()
// Check if a file should be transformed with this tsconfig's options
if (tsconfig && isFileIncluded(tsconfig, absoluteFilePath)) {
const { compilerOptions } = tsconfig.config
// Pass to esbuild, SWC, etc. as tsconfigRaw
}
// Resolve path aliases (returns candidate paths — check which exist)
const resolved = tsconfig && resolvePathAlias(tsconfig, '@/utils/helper')
// → ['/project/src/utils/helper'] or []
The nearest tsconfig typically applies. Use getTsconfig with the file path — it walks up and finds the right one:
const cache = new Map()
const getConfigForFile = (filePath: string) =>
getTsconfig(filePath, { cache })
Cache deduplicates filesystem reads across calls. Create a new Map() to invalidate after filesystem changes.
Implied options are already normalized — no need to check parent flags:
const { compilerOptions } = getTsconfig().config
compilerOptions.noImplicitAny // true (implied by strict: true)
compilerOptions.strictNullChecks // true (implied by strict: true)
compilerOptions.esModuleInterop // true (implied by module: 'nodenext')
compilerOptions.allowJs // true (implied by checkJs: true)
Options not set and not implied remain undefined (not false). Use ?? false for boolean checks.
import { getExtendsChain } from 'get-tsconfig'
const chain = getExtendsChain('./tsconfig.json')
const filesToWatch = chain.map(entry => entry.path)
import { getExtendsChain, resolveExtendsChain } from 'get-tsconfig'
const chain = getExtendsChain('./tsconfig.json')
chain[0].config.compilerOptions = {
...chain[0].config.compilerOptions,
sourceMap: true,
}
const result = resolveExtendsChain(chain)
// Default: nearest tsconfig (tsc CLI behavior)
getTsconfig('./src/index.ts')
// Validates file is a root file before accepting (VS Code behavior)
getTsconfig('./src/index.ts', { includes: true })
isFileIncludedChecks whether a file matches include/exclude/files globs — whether it's a root file. This is NOT the same as "is this file part of the TypeScript program."
| Source | What it adds | Checked by isFileIncluded? |
|--------|-------------|-------------------------------|
| include/files globs | Root files | Yes |
| Transitive imports | Files imported by root files (recursive) | No |
| @types packages | Auto-discovered from node_modules/@types/ | No |
| Triple-slash directives | /// <reference path="..." /> | No |
exclude only filters glob matching — if a root file imports an excluded file, that file is still in the program.isFileIncluded returning false doesn't mean the file won't be compiled — it may be pulled in via imports.getTsconfig(filePath) without includes.| Issue | Detail |
|-------|--------|
| Immutable tsconfig objects | isFileIncluded and resolvePathAlias cache per object identity. Do not mutate after first call. |
| extends must be resolved | isFileIncluded throws if config.extends is present. Use getTsconfig/readTsconfig output. |
| resolvePathAlias returns candidates | Returns paths from compilerOptions.paths, not verified files. Check existence yourself. |
| getExtendsChain resolves extends | The extends field in each entry is an absolute path, not the original string. |
development
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
tools
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
development
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
tools
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).