project-discovery

Featured

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 263 stars 23 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
81
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` - personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. # 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....

Details

Author
testdouble
Repository
testdouble/han
Created
4 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

Code & Development Listed

repo-discovery

Use when the user says 'explore this repo', 'what does this codebase do', 'give me an overview of this repo', 'onboard me to this project', or opens work in an unfamiliar repo before making changes. Read-only: surface scan, entry points (README/CLAUDE.md/ARCHITECTURE.md), source tree, key files.

0 Updated 1 weeks ago
oliver-chase
Data & Documents Featured

architectural-analysis

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.

263 Updated today
testdouble
Code & Development Listed

explore

Get familiar with any codebase. Deep-dive tech stack, architecture, features, conventions, issues. Multi-repo support. Keywords: explore, understand, onboard, what is this, how does it work, codebase, repo, project, analyze

2 Updated yesterday
jvalin17