zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-03-30 13:43:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(skills): tighten repo-scan install flow

Browse Source
This commit is contained in:
Affaan Mustafa
2026-03-28 20:29:51 -04:00
parent 57e9983c88
commit dcc4d914d2
1 changed files with 15 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
skills/repo-scan/SKILL.md
View File

@@ -18,10 +18,14 @@ origin: community
## Installation ## Installation
```bash ```bash
# Clone at a pinned commit for reproducibility # Fetch only the pinned commit for reproducibility
git clone https://github.com/haibindev/repo-scan.git mkdir -p ~/.claude/skills/repo-scan
cd repo-scan && git checkout 2742664 git init repo-scan
cp -r ../repo-scan ~/.claude/skills/repo-scan cd repo-scan
git remote add origin https://github.com/haibindev/repo-scan.git
git fetch --depth 1 origin 2742664
git checkout --detach FETCH_HEAD
cp -r . ~/.claude/skills/repo-scan
``` ```
> Review the source before installing any agent skill. > Review the source before installing any agent skill.
@@ -48,9 +52,11 @@ cp -r ../repo-scan ~/.claude/skills/repo-scan
## How It Works ## How It Works
1. **Scan**: `/repo-scan` runs a pre-scan pass to classify files and detect dependencies 1. **Classify the repo surface**: enumerate files, then tag each as project code, embedded third-party code, or build artifact.
2. **Analyze**: AI reviews the structured data and assigns verdicts per module 2. **Detect embedded libraries**: inspect directory names, headers, license files, and version markers to identify bundled dependencies and likely versions.
3. **Report**: Interactive HTML report generated with verdict distribution and drill-down 3. **Score each module**: group files by module or subsystem, then assign one of the four verdicts based on ownership, duplication, and maintenance cost.
4. **Highlight structural risks**: call out dead-weight artifacts, duplicated wrappers, outdated vendored code, and modules that should be extracted, rebuilt, or deprecated.
5. **Produce the report**: return a concise summary plus the interactive HTML output with per-module drill-down so the audit can be reviewed asynchronously.
## Examples ## Examples