scan-orphan-components
Skill2 starsChanged 7 months agoMITView on GitHub
扫描前端目录,找出无任何 import 引用的孤儿组件文件,输出候选删除清单
In this repository26 other files it gives its agents.
- advise-tech-stackSkill
- commit-with-affectsSkill
- db-dev-guideSkill
- export-db-indexesSkill
- frontend-dev-guideSkill
- frontend-ux-evaluatorSkill
- generate-pr-descriptionSkill
- generate-test-from-impactSkill
- generate-test-skeletonSkill
- lock-global-conventionsSkill
- plan-component-hierarchySkill
- plan-page-mapSkill
- proposal-reviewSkill
- propose-workflow-improvementsSkill
- pr-self-reviewSkill
- record-decisionSkill
- review-guardrailsSkill
- run-pending-specsSkill
- run-testsSkill
- scan-bundle-bloatSkill
- scan-code-hygieneSkill
- scan-dead-routesSkill
- scan-frontend-qualitySkill
- scan-unused-exportsSkill
- sync-llm-contextSkill
- verify-specSkill
The file
Files
Scan Orphan Components Skill
单独调用:
/scan-orphan-components在工作流中调用:由slim工作流 Phase 1 自动触发 前置要求:必须先读取.slimignore(如存在),豁免文件不参与扫描
执行步骤
Step 1:读取豁免清单
若 .slimignore 存在,读取所有豁免路径。若不存在,记录 [WARN] .slimignore 不存在,建议创建以保护动态引用文件,继续执行(不中止)。
Step 2:列出所有组件文件
列出 {{FRONTEND_PATH}}/components/ 和 {{FRONTEND_PATH}}/pages/(及 views/)下所有文件,过滤掉命中 .slimignore 的路径。
Step 3:全库引用搜索
对每个候选文件,在整个仓库搜索是否有其他文件 import 它:
# 搜索方式:文件名(无扩展名)作为 import 目标
grep -rn "from.*ComponentName\|import.*ComponentName" {{FRONTEND_PATH}} --include="*.{{EXT}}"
# 同时搜索动态 import / lazy 加载
grep -rn "import(.*ComponentName\|React.lazy.*ComponentName" {{FRONTEND_PATH}} --include="*.{{EXT}}"零静态引用且未豁免 → 列为候选。 有动态 import 引用(字符串形式)→ 标注 🟡 中风险,需人工确认。
Step 4:收集元数据
对每个候选文件执行 git log --follow -1 --format="%ad %an" -- <file> 获取最后修改信息。
输出格式
## 孤儿组件扫描结果
扫描路径:{{FRONTEND_PATH}}
豁免文件:N 个(来自 .slimignore)
候选文件:M 个
| 文件 | 最后修改 | 作者 | 风险 | 备注 |
|------|---------|------|------|------|
| src/components/OldWidget.tsx | 2024-01-05 | - | 🟢 低 | 零引用 |
| src/components/LegacyTable.tsx | 2024-03-10 | - | 🟡 中 | 疑似动态加载 |
⚠️ 以上文件未在 .slimignore 中声明,建议人工确认后再决定删除。约束
- NEVER 自动删除任何文件,只输出报告
- MUST 同时搜索静态 import 和动态 import(字符串形式的懒加载)
- MUST
.slimignore命中的文件不出现在候选列表中
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.

