Skip to content
cccskills
FreePublished on GitHub

survey-patterns

Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change, reading any source the task names outside this repo. 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.1 KB
  • references/pattern-surveyor.md6.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Survey Patterns

Search the codebase for analogous features and reusable building blocks before planning a change, and read any source the task names outside this repo. 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", no name). Wait for it to report before continuing; do not relaunch it if it has not yet reported. Its prompt must direct it to treat the shared working tree and its git index as read-only and to survey by reading and reasoning. HEAD stays where it is: read other refs with git show <ref>:<path> rather than git checkout or git switch. The subagent's prompt must include:

  1. The confirmed task description from Step 1
  2. 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, reads any external source the task names, 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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".

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

Audit the turbo skill lessons that /self-improve writes into this repo's .turbo/handoff/ from other projects, apply the ones the user approves, delete the consumed handoffs, commit and push, and update the installed Turbo skills. Use when the user asks to "read .turbo/handoff and let me know what you think", "read the handoff files and let me know what you think", "review the lesson handoffs", "apply the self-improve handoffs", or "process the turbo handoffs".

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. 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", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to "claude print", "ask claude", "run claude", "consult claude", or when a Codex Turbo skill needs Claude as an independent peer reviewer.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 21, 2026

See all skills by tobihagemann

Report a problem with this skill