AGENT SKILL

native-evidence-review

Manually audit traceability and limits of an existing authorized native-game or reverse-engineering handoff, connecting evidence to findings, behavior contracts and test results. Use before a specialist handoff or acceptance review. Adapted for existing DSI/REA records; not a new case ledger, target-analysis tool, provenance clearance or acceptance authority.

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
native-evidence-review
description
Manually audit traceability and limits of an existing authorized native-game or reverse-engineering handoff, connecting evidence to findings, behavior contracts and test results. Use before a specialist handoff or acceptance review. Adapted for existing DSI/REA records; not a new case ledger, target-analysis tool, provenance clearance or acceptance authority.

02 资源文件 4

03 SKILL.md 正文

Native Evidence Review

Adapted from zhaoxuya520's reverse-skill case-review under MIT. See SOURCE.md for its pin and omissions. This manual companion needs no upstream checkout, Python script, bootstrap, executable helper, new provider or case format.

Establish the boundary

Confirm the authorized evidence set, owning specification, current artifact/source identities, destination and acceptance owner. Read existing DSI/spec/TDD/REA conventions where already used. Preserve source/provider choices; this companion does not activate another router or grant target access.

Review supplied, already authorized records read-only. Do not initialize work/case directories, create scope/timeline/evidence ledgers, install tools, run target analysis, read original game data, capture a process or change the target. Report missing input/access precisely; do not manufacture records or retrieve additional private material without authority.

For Rock Man x64 retain no BIOS/emulator runtime, independent implementation, source-eligibility/PSX-SPX holds, stopped initializer/IDE and S2 gates. Review and hash agreement do not clear rights, certify clean-room work, supply a Mega Man Legends oracle or establish boot.

Review the chain

Use review-checklist.md for details. Map the existing record's terminology; do not impose upstream Evidence/Finding/Path IDs.

  1. Bind claims to a bounded question, exact version/region/revision or artifact where relevant, permitted source, tool/version and address/time convention. Unknown stays unknown.
  2. Resolve existing evidence references. Distinguish observed, derived/inferred, proposed and unknown; preserve contradictions and negative results. Mirrors of one source are not independent confirmation.
  3. Connect eligible findings to the smallest provider-owned requirement and acceptance criterion. Record initial state, input, sequence/timing, output/error and reset/tolerances when known. Static pseudocode is a hypothesis, not observed gameplay. Label native-design choices honestly.
  4. Identify genuine RED/GREEN or characterization, regressions and review. Separate synthetic/component checks from real MSVC/Windows execution, visual/audio/input checks, eligible reference comparison and full-product integration.
  5. Inspect recorded SHA-256 and artifact identities. Recompute only with already available read-only tooling and authorized file reads; never fetch a missing original or follow a path outside the approved boundary. A matching hash is byte identity with that digest, not correctness/provenance/permission. Preserve mismatches and stop relying on that artifact; do not silently replace it.
  6. Return blockers, unresolved claims, existing owner and next scoped action. Do not modify acceptance flags or publish without applicable authority.

Output

Use the user's language and existing handoff format: scope/pins; supported claims with existing evidence IDs; missing links/contradictions; fixity checked/not-run; test/platform/oracle limits; exact owner/action for blockers. Pass/needs-work/blocked describes this review only, not product acceptance.

Keep sensitive source, bytes, captures, paths and identities in the existing private destination. Authorized public summaries use original sanitized prose and approved links/IDs. Do not copy the upstream journal or historical-authorization claims.

The byte-preserved upstream entrypoint is source history only; do not follow its script/bootstrap/case-initialization route.

04 同仓库更多 Skills