tobihagemann/survey-patterns
skills/survey-patterns/SKILL.md
Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to "survey patterns", "find existing patterns", "look for analogous features", "check how similar things are done", "find prior art for this change", or needs pattern context before planning a change.
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo survey-patternsInstall 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: Apr 20, 2026, 4:24 AM13.4s2 files scanned
SKILL.md
- name:
- survey-patterns
- description:
- Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to \"survey patterns\", \"find existing patterns\", \"look for analogous features\", \"check how similar things are done\", \"find prior art for this change\", or needs pattern context before planning a change.
Survey Patterns
Search the codebase for analogous features and reusable building blocks before planning a change. Returns structured findings. Does not write code or plans.
Step 1: Identify the Task
Determine what the change is about:
- If a task description was passed in, use it
- Otherwise, derive it from conversation context (the user's latest request)
State the task back in one sentence to confirm scope before searching.
Step 2: Spawn Pattern Survey Subagent
Spawn a single subagent (model: "opus", do not set run_in_background). The subagent's prompt must include:
- The confirmed task description from Step 1
- An instruction to read references/pattern-surveyor.md for survey guidelines, categories, and output format before searching
The subagent covers all three categories (Analogous Features, Reusable Utilities, Convention Anchors) in one sweep and returns a single structured report.
Step 3: Output Findings
Output the subagent's report verbatim. Do not reformat or re-synthesize — references/pattern-surveyor.md specifies the exact output format the subagent produces.
Then use the TaskList tool and proceed to any remaining task.
Rules
- Do not write files.
- Do not propose implementation steps.
Related Skills
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/assess-technical-debt
development
VerifiedTrustedCommunity
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", or "what's our worst code". Analysis-only — does not modify code.
377SKILL.mdUpdated Jun 15, 2026
tobihagemann/simplify-docs
development
VerifiedTrustedCommunity
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".
377SKILL.mdUpdated May 15, 2026