mikeparcewski/change-type-detector
skills/crew/change-type-detector/SKILL.md
Classifies a list of file paths into change types (ui, api, both, unknown) using an explicit two-pass decision algorithm: extension matching first, then path-segment matching for ambiguous cases. Use when: "detect change type", "classify files", "what kind of change", "ui or api change", "change-type detection", or before creating test tasks.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden change-type-detectorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:22 AM144.7s2 files scanned
SKILL.md
- name:
- change-type-detector
- description:
- |
- using an explicit two-pass decision algorithm:
- extension matching first,
- Use when:
- detect change type", "classify files", "what kind of change",
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Change Type Detector Skill
Classify file paths to determine which test types are needed.
Output Format
{
"change_type": "ui|api|both|unknown",
"ui_files": [...],
"api_files": [...],
"ambiguous_files": [...],
"confidence": 0.0-1.0,
"reasoning": "file1: reason; file2: reason; ..."
}
Two-Pass Classification Algorithm
Apply to EACH file independently, then combine results.
Pass 1 — Extension Matching (ordered)
Rule 1.1 — UI Extensions (unambiguous by default)
Files with these extensions classify as ui:
.tsx, .jsx, .vue, .svelte, .html, .htm, .css, .scss, .sass, .less
Exception — .tsx-in-api/ override rule (apply before returning ui):
If a UI-extension file has API path segments (api, routes, controllers,
handlers, endpoints, server, backend, services, graphql, rest, grpc,
middleware, resolvers, mutations, queries) AND no UI path segments,
AND the task description contains API keywords — classify as api.
Otherwise keep ui (extension wins).
Rule 1.2 — API-Confirming Extensions
Files with .py, .rb, .go, .java, .kt, .rs, .cs, .php, .scala, .clj, .ex, .exs:
- If path has API segments →
api - If path has UI segments →
ambiguous(treat as both) - Otherwise →
api(default for backend languages)
Rule 1.3 — Ambiguous Extensions
Files with .ts, .js, .mjs, .cjs → proceed to Pass 2.
Rule 1.4 — Unrecognized Extensions
All other extensions (.md, .yaml, .json, .sh, Makefile, etc.):
- If path has UI segments only →
ui - If path has API segments only →
api - If path has both →
ambiguous - If path has neither →
unrecognized(does not contribute to change type)
Pass 2 — Path Segment Matching (for .ts/.js/.mjs/.cjs only)
Check path segments (split on /, lowercase) against segment tables.
| Outcome | Condition |
|---------|-----------|
| ui | Has UI segment, no API segment |
| api | Has API segment, no UI segment |
| Use task description | Has both UI and API segments |
| Use task description | Has neither UI nor API segment |
Task description tiebreaker: tokenize description on non-alphanumeric characters, check against API keywords and UI keywords (see File Classification Rules).
- API keywords only →
api - UI keywords only →
ui - Both or neither →
ambiguous
Combining File Results
After classifying all files:
| Files Present | change_type | confidence |
|---------------|-------------|------------|
| Only ui_files | ui | 1.0 |
| Only api_files | api | 1.0 |
| Both ui + api | both | 0.9 |
| ambiguous_files present | promotes to both | 0.7 |
| Only unrecognized | unknown | 0.8 |
| No files | unknown | 1.0 |
Ambiguous files are conservative: they promote the result to both (over-inclusive).
Quick Decision Table
| Extension | Path Signals | Task Keywords | Result |
|-----------|-------------|---------------|--------|
| .tsx/.jsx/.vue/.svelte | — | — | ui |
| .tsx + api/ path | API kws in desc | yes | api |
| .css/.scss/.sass/.less | — | — | ui |
| .html/.htm | — | — | ui |
| .py/.rb/.go/.java/.kt | api/ path | — | api |
| .py/.rb/.go/.java/.kt | — (no path) | — | api |
| .ts/.js | components/ | — | ui |
| .ts/.js | api/ routes/ | — | api |
| .ts/.js | neither | API kws | api |
| .ts/.js | neither | UI kws | ui |
| .ts/.js | neither | neither | ambiguous |
| .md/.yaml/.json | — | — | unrecognized |
See File Classification Rules for the complete extension tables, path segment tables, and keyword lists.
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
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.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
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.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
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).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
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).
8SKILL.mdUpdated Jul 15, 2026