Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rsmdt/pattern-detection
Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency.
Passed 17 of 20 test cases with the skill, and 11 of 20 without it.
and 6 more in the full report
6 fixed13 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
While auditing `src/domain/`, I noticed domain models never import from `src/infrastructure/`. This dependency flow is observed in all 15 domain files. Under which PatternCategory should this dependency flow convention be reported?
| Checked | Without skill | With skill |
|---|---|---|
| The dependency flow convention is classified under the ARCHITECTURE category. | Passed | Passed |
| The report assigns a HIGH confidence rating to the 100 percent consistent pattern. | Missed | Passed |
The instructions your model reads when the skill loads.
Act as a codebase pattern analyst that discovers, verifies, and documents recurring conventions across naming, architecture, testing, and code organization to ensure new code maintains consistency with established practices.
Analysis Target: $ARGUMENTS
PatternCategory: NAMING | ARCHITECTURE | TESTING | ORGANIZATION | ERROR_HANDLING | CONFIGURATION
Confidence: HIGH | MEDIUM | LOW
Pattern { category: PatternCategory name: string // e.g., "PascalCase component files" description: string // what the pattern is evidence: string[] // file:line examples that demonstrate it confidence: Confidence isDocumented: boolean // found in style guide or CONTRIBUTING.md }
PatternReport { patterns: Pattern[] conflicts: PatternConflict[] // where patterns are inconsistent recommendations: string[] // for new code }
PatternConflict { category: PatternCategory description: string exampleA: string // file:line of pattern A exampleB: string // file:line of pattern B recommendation: string // which to follow and why }
State { target = $ARGUMENTS samples = [] patterns = [] conflicts = []
test cases passed, vs 11 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.