菜单
Validate LEAPP artifact path globs against real extraction file listings before committing them. Use when adding or changing a "paths" pattern in __artifacts_v2__, when an artifact returns no rows and the pattern is suspect, or when a vendor has moved a file between OS versions.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/abrignoni/iLEAPP --skill leapp-validate-globs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Wire up how an artifact renders in LAVA, end to end across the producer and the viewer. Use when adding a conversation view to an artifact, when a view renders wrong or not at all, when adding a field to the LAVA schema or manifest, or when asked to "add a module to the LAVA schema".
Run a LEAPP tool end to end against a real extraction to validate artifact changes and produce a handoff. Use when verifying new or changed artifacts before a PR, when asked to "run it against a real image" or "check the report", or when confirming recorded sample_data row counts.
Write a new LEAPP artifact module, or substantially rework an existing one. Use when adding support for an app or data source in iLEAPP, ALEAPP, RLEAPP, VLEAPP or DLEAPP, when asked to "add an artifact" or "parse <app>", or when a module needs new output types, media or a conversation view.
基于 SOC 职业分类
| name | leapp-validate-globs |
| description | Validate LEAPP artifact path globs against real extraction file listings before committing them. Use when adding or changing a "paths" pattern in __artifacts_v2__, when an artifact returns no rows and the pattern is suspect, or when a vendor has moved a file between OS versions. |
A pattern that matches nothing fails silently. The artifact simply reports no data, which is indistinguishable from the app not being present. Never commit a pattern you have not run.
The matcher is Python fnmatch, so reproduce it exactly rather than approximating with
glob or a regex:
* and ** both span /. They are interchangeable.os.path.normcase, so it is case-sensitive on macOS and Linux
and case-insensitive on Windows. Test the case-sensitive behaviour; it is the stricter one.root/. iLEAPP's iOS-backup seeker
does not, and does not normcase either.iLEAPP carries real file listings from published research images at
admin/data/filepath-lists/*.csv.zip, covering several iOS generations.
Unzip to a scratch directory, then run each candidate pattern over the path column with
fnmatch.fnmatchcase and count hits per generation. Run the old and new patterns both,
and compare. A change that reduces the count on an older image is a regression, not a
tightening, unless you meant it.
Instantiate the matching seeker from scripts/search_files.py directly so the semantics are
exact by construction, then call search() with the pattern. This is the only way to catch
a mismatch between what you think the seeker does and what it does.
To confirm the artifact then produces the rows you expect, call the artifact function's
.__wrapped__, exposed by @artifact_processor's @wraps, with a mock context providing
get_files_found() and get_relative_path(). len(data_list) is the count to record in
sample_data.
Case variants. Use one bracket class, */[Bb]iome/*, never a tuple of two patterns. A
tuple double-counts on Windows, where normcase folds both to the same string and the
entry point extends files_found once per pattern with no dedup.
Vendor moves. When a file changes location between OS versions, keep the old pattern alongside the new one. Examiners run these tools against extractions going back years.
Over-generic components. A pattern whose filename component is bare *, ** or *.*
matches every file at that level and is rejected. Anchor on something real.
Print counts and value shapes from test images, never actual values, and delete anything you extracted when you are done.