Run any Skill in Manus with one click

Get Started

ts-search-first

Stars8

Forks0

UpdatedApril 4, 2026 at 14:51

Before writing any new function, hook, type, or component, search the codebase for existing implementations to reuse.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Antune-L

Antune-L/skillzer

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ts-search-first
description	Before writing any new function, hook, type, or component, search the codebase for existing implementations to reuse.
metadata	{"short-description":"Codebase-first (reuse before creation)"}

Why this exists

Claude defaults to generating fresh implementations even when existing code is a 90% match. This skill forces a search-first habit to catch reuse opportunities before writing anything.

Procedure

Never start by coding. Start by locating what already exists.
Search the codebase by:
- Probable names (camelCase, PascalCase, kebab-case)
- Types/interfaces/export names
- Patterns (useXxx, XxxProvider, getXxx, buildXxx, createXxx, updateXxx)
- Routes/paths (backend) and query keys (frontend)
Use fast searches (e.g. ripgrep):
- rg "use[A-Z]" src
- rg "function <name>|const <name> =" src
- rg "<TypeName>" src
- rg "<route-path>" src
If found:
- Propose direct reuse, or minimal extension
- Respect local conventions (folders, naming, exports)
If not found:
- Create the smallest possible solution, consistent with existing architecture

Output

Short report: "Found / not found" + files examined.
Then the proposal: reuse (preferred) or minimal implementation.

Composability

Run coding-convention after extending found code to verify naming/file placement.
Run regression-check after modifying existing code to catch broken consumers.

Gotchas

When creating a new oRPC contract/schema, also search for reusable utility schemas (pagination, search, sort, userId filters) — not just routes. Missing these leads to duplicated schemas discovered only at review time.
Search for aliased re-exports — exact name matches miss code that re-exports under a different name.
In monorepos, search all workspace packages, not just src/. Duplicate utilities across packages are common.

More from this repository

same repository

argus-review

Antune-L/skillzer

When asked to review a PR or branch ("review this PR", "PR review", "argus", before merging), fan the diff out to parallel read-only reviewers and return a severity-ranked verdict; optionally post inline via gh.

2026-07-078

minos-pr-feedback

Antune-L/skillzer

When the user has reviewer feedback on a GitHub PR (human or bot like gemini-code-assist) and wants the pertinent items fixed — "j'ai des retours sur la PR", "résous/corrige ce qui est pertinent", "lis les commentaires de la PR via gh" — triage every comment thread via gh, apply only the pertinent fixes (drop nits), then reply to and resolve each triaged thread. Not for publishing our own review findings — that is argus-review --post.

2026-07-078

audit-agents-skills

Antune-L/skillzer

Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.

2026-07-048

coding-convention

Antune-L/skillzer

Enforce project coding conventions: reduce duplication, keep naming/file placement consistent, and minimize regression risk. Includes React component and layout guidelines. Use when writing or reviewing code.

2026-07-048

prd

Antune-L/skillzer

Generate a Product Requirements Document from user instructions using the PRD template. Outputs a human-readable self-contained HTML file plus a markdown source for implementation tooling. Includes a macro-level task checklist at the end.

2026-07-048

regression-check

Antune-L/skillzer

After modifying code, map all consumers of changed symbols and flag unhandled mismatches. Not for debugging (use systematic-debugging).

2026-07-048

name	ts-search-first
description	Before writing any new function, hook, type, or component, search the codebase for existing implementations to reuse.
metadata	{"short-description":"Codebase-first (reuse before creation)"}

Why this exists

Claude defaults to generating fresh implementations even when existing code is a 90% match. This skill forces a search-first habit to catch reuse opportunities before writing anything.

Procedure

Never start by coding. Start by locating what already exists.
Search the codebase by:
- Probable names (camelCase, PascalCase, kebab-case)
- Types/interfaces/export names
- Patterns (useXxx, XxxProvider, getXxx, buildXxx, createXxx, updateXxx)
- Routes/paths (backend) and query keys (frontend)
Use fast searches (e.g. ripgrep):
- rg "use[A-Z]" src
- rg "function <name>|const <name> =" src
- rg "<TypeName>" src
- rg "<route-path>" src
If found:
- Propose direct reuse, or minimal extension
- Respect local conventions (folders, naming, exports)
If not found:
- Create the smallest possible solution, consistent with existing architecture

Output

Short report: "Found / not found" + files examined.
Then the proposal: reuse (preferred) or minimal implementation.

Composability

Run coding-convention after extending found code to verify naming/file placement.
Run regression-check after modifying existing code to catch broken consumers.

Gotchas

When creating a new oRPC contract/schema, also search for reusable utility schemas (pagination, search, sort, userId filters) — not just routes. Missing these leads to duplicated schemas discovered only at review time.
Search for aliased re-exports — exact name matches miss code that re-exports under a different name.
In monorepos, search all workspace packages, not just src/. Duplicate utilities across packages are common.