survey-patterns
survey-patterns searches a codebase for analogous features, reusable utilities, and existing conventions relevant to a proposed change. Use this skill when you need to understand how similar functionality is already implemented or what building blocks exist before planning a modification, ensuring changes align with established patterns without duplicating effort.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/survey-patterns && cp -r /tmp/survey-patterns/claude/skills/survey-patterns ~/.claude/skills/survey-patternsSKILL.md
# 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: 1. The confirmed task description from Step 1 2. An instruction to read [references/pattern-surveyor.md](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.
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".
Run AI-powered code review using the codex CLI. Use when the user asks to \"codex review\", \"run codex review\", or \"review a commit with codex\".
Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.