large-file-lfslisted

# Large File LFS ## Core Question Are large, binary, generated, or LFS-managed files being handled correctly for the requested Git action? ## When To Use Use this skill when: - large or binary files appear in staged, unstaged, or untracked work - the user asks whether files should use Git LFS - generated artifacts might be accidentally committed - preflight detects file-size or binary risks ## When Not To Use Do not use this skill when: - secret detection - rewriting history to remove already-pushed large files - normal commit grouping - general `.gitignore` authoring without size/binary evidence Route to: - secret-like content routes to `secret-scan` - already committed or pushed large-file recovery routes to `undo-recover` - commit exclusion routes to `atomic-commits` - ignore rule edits may be handled by the repository editing workflow ## Required Evidence Before action, inspect or establish: - staged/unstaged/untracked file list - file sizes and binary indicators - `.gitattributes` and LFS tracking rules - generated/build directory patterns - whether file is already committed or pushed - project policy for artifacts No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a pl