| name | same-set-reusable-flow-for-project-file-inventor |
| version | 0.1.0 |
| author | Meta_Kim |
| user-invocable | false |
| candidateType | skill |
| sourceGapId | gap-create-skill-same-set-reusable-flow--c89068df05 |
| approvalEvidence | warden-approved-file-inventory-skill-2026-06-05 |
| trigger | project file inventory|file classification|repo cleanup|项目文件整理|文件用途整理|清理项目 |
| tools | ["shell","filesystem"] |
| description | Reusable Meta_Kim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
|
Project File Inventory Classification
Use this skill when a Meta_Kim workspace has too many files and the user needs to know which are useful, generated, risky, or safe to ignore.
Goal
Produce a source-backed inventory, not a cleanup guess. The output should help the user decide what to keep, commit, ignore, or inspect again.
Required Evidence
Start with read-only evidence:
git status --short --branchgit ls-filesgit ls-files --others --exclude-standardgit check-ignore -v <path> for suspicious ignored pathsrg -n "<filename-or-command>" package.json docs scripts tests canonical config for tracked candidatesnpm run script inventory from package.json
Do not classify a tracked file as removable only because it has few references. Check package scripts, tests, docs, sync scripts, setup scripts, and contracts first.
Classification Buckets
- Core source:
canonical/, config/contracts/, config/capability-index/, durable scripts, package scripts, and tests that define behavior.
- Runtime projection:
.claude/, .agents/, .cursor/, openclaw/, .codex/ mirrors generated from canonical sources or sync scripts.
- Generated evidence:
.meta-kim/state/default/, graph outputs, reports, SQLite run state, smoke artifacts, and temporary proof files.
- Planning continuity:
task_plan.md, findings.md, progress.md; keep during active work even if ignored.
- Reference docs: tracked docs and plans that explain product, architecture, contracts, or release decisions.
- Suspicious or cleanup candidate: files with no package, test, docs, sync, install, contract, or runtime evidence.
Output Format
Return a compact table with:
- path or pattern
- bucket
- why it exists
- evidence command
- recommendation: keep, commit, ignore, regenerate, inspect again, or cleanup candidate
- risk if deleted
