patterns

Clusters Plumbline lint violations by shape and proposes bulk fixes.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill patterns-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patterns
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-plumbline/skills/patterns
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill patterns-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large codebases can accumulate hundreds of similar lint violations, and fixing them one at a time is impractical. This Skill groups Plumbline lint violations into clusters sharing the same shape so cleanup targets entire classes of problems at once. ## Core Features & Use Cases - Violation Clustering: Runs plumbline patterns . to group citation-unresolved violations by tag and comment-hygiene violations by shape (divider, license-fragment, todo-marker, commented-out-code, doc-residue, disallowed-prose). - Guided Bulk Fixes: For each cluster, proposes an appropriate action — bulk delete, license header reformatting, docstring opt-in markers, or fixing citation slugs. - Read-Only Safety: Proposes fixes but never applies them; every bulk deletion requires explicit user confirmation. - Use Case: After adopting the Plumbline methodology in a legacy project, run this Skill to turn 300 scattered lint violations into six actionable clusters with a proposed fix for each. ## Quick Start Ask the assistant to run /ok-plumbline:patterns to cluster the project's Plumbline lint violations and propose bulk fixes for each group.

Frequently Asked Questions about patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix hundreds of similar lint violations at once?▼

Run the patterns command to cluster violations by shared shape, then apply a bulk fix per cluster. The plumbline binary groups comment-hygiene violations by pattern and citation violations by tag, printing counts and example sites for each cluster.

What kinds of comment violations does Plumbline detect?▼

Plumbline detects six comment-hygiene shapes: divider, license-fragment, todo-marker, commented-out-code, doc-residue, and disallowed-prose. It also detects citation-unresolved violations, which cluster by tag such as tag:@concept: or tag:@story:.

Does the patterns command modify my source files?▼

No, the patterns workflow is read-only. It clusters violations and proposes fixes such as bulk deletion or slug correction, but nothing is applied without explicit user confirmation of each cluster shape.

Why does the skill prefer the vendored plumbline binary?▼

Clustering must reflect the exact lint rules the project lints against, so the vendored binary at .ok-plumbline/bin/plumbline is preferred. If absent, it falls back to the plugin payload copy and prints a note recommending /ok to pin one.

How do I handle doc-residue violations in public API files?▼

For block comments adjacent to declarations in files without an opt-in marker, add a // @plumbline:allow-docstrings line near the top if the file is a public API surface. Otherwise, propose deleting the residue.