Miller patterns audit

Skill anortham/miller/skills/miller-patterns-audit

Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.From its SKILL.md

Install

npx -y skills add anortham/miller --skill miller-patterns-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

Miller Patterns Audit

Use patterns when the question is about known structural facts emitted by julie-extractors, not arbitrary AST matching. Runtime list output is authoritative for the current catalog. Start by listing observed pattern IDs in the selected workspace, then search the relevant ID with path, language, and metadata filters.

Workflow

Discover available IDs:

patterns(operation="list")
patterns(operation="list", language="razor")

List output includes Next: / JSON next_actions derived from observed IDs. Prefer those follow-up calls before inventing a raw text grep.

Search a concrete pattern:

patterns(operation="search", pattern_id="aspnet.minimal_api.route.v1", where="verb=GET")
patterns(operation="search", pattern_id="htmx.attribute.v1", where="name=hx-get", path="Views/**")
patterns(operation="search", pattern_id="alpine.directive.v1", where="directive=x-data", path="Views/**")
patterns(operation="search", pattern_id="sql.merge_statement.v1")

Summarize before broad audits:

patterns(operation="summary", pattern_id="markdown.heading.v1", path="docs/**")
patterns(operation="summary", pattern_id="json.property.v1", language="json")

Inspect source only after the pattern rows identify a file and line:

inspect(target="<path from pattern row>")

Good Uses

List ASP.NET minimal API routes without scanning source text.
Find htmx or Alpine usage in Razor/HTML views.
Audit SQL DDL/DML, including MERGE, JSON/YAML/TOML keys, or Markdown structure.
Compare code-shape facts across registered workspaces with workspace_id.

Limits

patterns is not a raw AST query engine.
Pattern IDs come from the extractor catalog; if a shape is missing, add extractor support first.
No-match output can include near matches and active-filter guidance. If the pattern exists but filters remove every row, loosen path, language, or where.
Use search(mode="source") for arbitrary source text and search(mode="content") for docs/config prose.