skills.rest
Boulea7
Boulea7COMMUNITY
Explore all skills by this author →
GitHub

search-first

Searches the repository for existing solutions before writing new code or adding dependencies.

Updated Dec 1, 2025
Search Tags:#software engineering#refactoring#code reuse#repository search#decision workflow#dependency evaluation
One-click install
npx skills add https://github.com/Boulea7/ohmyclaude --skill search-first-boulea7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: search-first
Source: https://github.com/Boulea7/ohmyclaude/tree/main/src/ohmyclaude/templates/skills/search-first
Command: npx skills add https://github.com/Boulea7/ohmyclaude --skill search-first-boulea7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often add new dependencies or write custom helpers without checking whether the repository or an existing package already solves the problem, leading to duplicated code and unnecessary maintenance burden. ## Core Features & Use Cases - Repository Search Workflow: Guides a four-step process of searching the current repo, checking official tooling, comparing adoption cost, and only then building custom code. - Decision Rule: Provides a clear adopt / extend / build-custom decision framework based on fit and maintenance health. - Use Case: Before adding a new date-parsing utility, use this Skill to search the codebase for existing helpers and evaluate whether a maintained package already covers the need. ## Quick Start Before implementing this feature, search the repository for existing utilities or packages that already solve it and recommend whether to adopt, extend, or build custom.

Frequently Asked Questions about search-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid duplicating existing code in a repository?▼

Search the current repository for existing utilities, patterns, or configs before writing new code. Then check whether official tooling or an existing package already solves the problem, and only build custom code when existing options are clearly insufficient.

When should I add a new dependency versus writing custom code?▼

Adopt a dependency when the fit is strong and the package maintenance is healthy. Extend an existing solution with a small wrapper when it nearly closes the gap, and build custom only when search results are a poor fit.

How do I evaluate whether an existing package fits my use case?▼

Compare three factors: adoption cost, maintenance burden, and scope fit. A package with strong fit and healthy maintenance should be adopted, while a partial match may only need a small wrapper.

When is building custom code justified over reusing existing solutions?▼

Custom code is justified only when repository search results and existing packages are clearly a poor fit for the requirement. If a small wrapper around an existing solution closes the gap, prefer extending over building from scratch.

Related Skills

Explore More Software Engineering Skills→
HumandDevHumandDev

area-intake

Collect area objectives, repositories, dependencies, and constraints into a problem statement and checklist.

Official
Basic
YosefHayimYosefHayim

search-first

Search package managers, MCP, and GitHub before implementing custom code.

Community
Intermediate
Vivekmano27Vivekmano27

dependency-audit

Scan Node.js, Python, Go, and Rust dependencies for vulnerabilities and license conflicts.

Community
Advanced
githubgithub
38.5k

create-technical-spike

Create time-boxed technical spike documents for researching critical development decisions.

Official
Basic