codelib-discovery

Identify existing code implementations and prior decisions relevant to a topic across internal and public sources, summarizing results in a structured note with queries, hits, gaps, and recommendations.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/arashshahidi1997/projio --skill codelib-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codelib-discovery
Source: https://github.com/arashshahidi1997/projio/tree/main/docs/prompts/skills/codelib-discovery
Command: npx skills add https://github.com/arashshahidi1997/projio --skill codelib-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface existing code implementations, patterns, utilities, and prior decisions relevant to a topic, and capture results as a structured reference note to guide new work.

Core Features & Use Cases

  • Codebase reconnaissance: search internal code and documentation for relevant implementations and conventions.
  • Library discovery: examine Codio registry and third-party libraries to surface reusable patterns.
  • Use-case mapping: generate a structured note that summarizes hits, gaps, and recommended next steps for the topic.

Quick Start

Provide a TOPIC and run the discovery to surface existing internal and library code references.

Frequently Asked Questions about codelib-discovery

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

FAQPage Schema
How do I find existing code implementations before building a new feature?

To find existing code implementations, you can run a discovery process that searches internal code and documentation corpora first, then public libraries, summarizing relevant patterns and prior decisions into a structured reference note.

What is codebase reconnaissance and how does it surface reusable patterns?

Codebase reconnaissance is the process of searching internal code and docs to identify existing implementations and conventions. It surfaces reusable patterns by mapping hits, gaps, and recommended next steps into a reproducible structured note.

How do I search internal documentation for prior decisions relevant to my topic?

You can search internal documentation by providing a specific topic to the discovery process, which queries internal corpora to surface prior decisions and conventions, limiting findings to internal sources before checking public libraries.

Can I generate a reference note that summarizes gaps in my codebase for a specific topic?

Yes, you can generate a structured reference note that summarizes hits, gaps, and recommended next steps. The note includes sections on the queries run and the findings discovered across code and docs corpora.

Does library discovery search internal code before checking public third-party libraries?

Yes, library discovery limits findings to internal sources first, then examines public third-party libraries and registries to surface reusable patterns, ensuring internal conventions are prioritized before external solutions.

What are the limitations of code discovery for identifying gaps in documentation?

The discovery process is limited to querying available code and docs corpora, meaning it can only surface gaps where documentation or code exists to be searched, summarizing results into a reproducible note with recommended next steps.