project-analysis
Skill0 starsChanged 2 months agoMITView on GitHub
Analyze a repository before selecting skills or coding.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- AnyOrgName/php-skillstheir own version, first seen Nov 8, 2026
- britt/agent-skillstheir own version, first seen Oct 25, 2026
- tarrragon/claude-skillstheir own version, first seen Sep 1, 2026
- jeroenvanwissen/project-analysistheir own version, first seen Feb 26, 2026
- jiangtao/skillstheir own version, first seen Jan 29, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- britt/agent-skills★ 11same name
- AnyOrgName/php-skills★ 4same name
- jeroenvanwissen/project-analysis★ 1same name
- jiangtao/skills★ 1same name
- tarrragon/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use before any coding task when the project is unknown, existing, or being adopted into Product-Skills.
- Distinctive: line 24
Read this skill first; prefer read-only inspection.
- Distinctive: line 61
No coding or mass file changes happen during analysis alone.
- Distinctive: line 65
Do not rewrite the repository during analysis.
- Distinctive: line 66
Do not invent Vue / Angular / Svelte support paths.
- Distinctive: line 67
Do not claim FSD compliance without evidence.
- Very specific: line 68
Follow rules/security.md for secrets and permissions.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
project-analysis
When to use
Use before any coding task when the project is unknown, existing, or being adopted into Product-Skills.
Purpose
Produce a Project Analysis Report so the agent installs and loads only required skills, and avoids silent architecture changes.
Inputs
- Repository path or workspace
- User request / product intent
- Access to manifests, source layout, CI, and docs
Process
- Read this skill first; prefer read-only inspection.
- Detect project type, language, framework, and folder structure.
- Detect architecture pattern (including FSD adoption) and conventions.
- Detect testing approach, security requirements, and deployment model.
- Recommend workflow and the minimum skill set from
skills/index.yaml. - List potential risks and what must not be changed without approval.
Outputs
Project Analysis Report:
Current state:
- project type:
- technology:
- architecture:
- conventions:
- testing:
- security:
- deployment:
Recommended workflow:
- ...
Required skills:
- ...
Potential risks:
- ...Also update .ai-review/change-summary.md when analysis informs an adoption plan.
Verification
- Report is reviewable by Product and Development.
- Recommendations stay within React + TypeScript + FSD for implementation skills.
- No coding or mass file changes happen during analysis alone.
Restrictions
- Do not rewrite the repository during analysis.
- Do not invent Vue / Angular / Svelte support paths.
- Do not claim FSD compliance without evidence.
- Follow
rules/security.mdfor secrets and permissions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.