project-discovery
SolidDiscovers 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.
Install
Quality Score: 86/100
Skill Content
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
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.
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.
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.