project-discovery

Solid

Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a concise reference section directly into the project's AGENTS.md or CLAUDE.md for other skills, agents, and hooks to consume. Use when scanning, analyzing, or detecting the project's technology stack, build tools, or repository structure. Does not create or update project documentation — use project-documentation for writing feature or system docs.

Code & Development 128 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Project Context - Default branch: !`git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknown` - AGENTS.md: !`find . -maxdepth 1 -name "AGENTS.md" -type f` - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - README: !`find . -maxdepth 1 -name "README*" -type f` # Project Discovery This skill discovers the project's core attributes and writes them as a concise `## Project Discovery` section **directly into the project's AGENTS.md or CLAUDE.md** — not a separate file. The output is small by design: a few notes on where things live, the languages and frameworks, and the commands to run, so an AI agent working in the repo can find its way around. It is not an exhaustive inventory. ## Step 1: Choose and read the target file Pick the single file this discovery is written into, by priority: 1. If **AGENTS.md** exists (the label above is non-empty), the target is AGENTS.md. 2. Otherwise, if **CLAUDE.md** exists, the target is CLAUDE.md. 3. If neither exists, the target is a new **CLAUDE.md** at the repository root, which you will create in Step 4. If the target file already exists, read it in full and build the **deduplication baseline**: a list of everything the file already documents that this skill would otherwise write — directory and folder locations, languages, frameworks, package manager, build/test/lint/dev commands, and the docs, ADR, and coding-standards directories. Note whether the file already has a `## Project Discovery` section....

Details

Author
testdouble
Repository
testdouble/han
Created
2 months ago
Last Updated
today
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

capability-discovery

Discover available agents, skills, quality commands (lint, test, typecheck), tech stack, verification capabilities, and LSP code intelligence features via parallel environment scanning. Use when starting implementation, creating PRs, reviewing PRs, or addressing feedback. This skill MUST be consulted because assuming tools exist causes runtime failures, and assuming they do not causes missing capabilities.

6 Updated today
synaptiai
AI & Automation Solid

project-onboarding

Scan an unfamiliar codebase, generate CLAUDE.md + OVERVIEW.md, and capture domain knowledge that code alone can't tell you. This skill should be used when the user wants to understand a new project, onboard onto a codebase, set up project documentation, create or update CLAUDE.md, or map project architecture. Common triggers include "what does this project do", "help me get started", "I just joined this repo", "document this codebase", "set up dev docs". Also applies when working on any unfamiliar or inherited project, even without an explicit onboarding request — if the user seems lost in a new codebase, this skill can help.

3 Updated yesterday
Wubabalala
Data & Documents Solid

project-documentation

Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.

128 Updated today
testdouble