Skip to content

mrc4tt/CS2_VibeSignatures / .claude/skills/find-CFlattenedSerializers_CreateFieldChangedEventQueue-decompiles

find-CFlattenedSerializers_CreateFieldChangedEventQueue-decompiles

Verified

Agent fallback for CFlattenedSerializers_CreateFieldChangedEventQueue-decompiles (auto-generated, category: func). Locate CFlattenedSerializers_CreateFieldChangedEventQueue in the CS2 networksystem module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CFlattenedSerializers_CreateFieldChangedEventQueue-decompiles, CFlattenedSerializers_CreateFieldChangedEventQueue

Find CFlattenedSerializers_CreateFieldChangedEventQueue-decompiles

Target: CFlattenedSerializers_CreateFieldChangedEventQueue (func) in the module loaded in THIS session.

The old artifact/preprocessor anchors no longer match this build. Use anchors only to locate candidates; derive the artifact from the ACTUAL bytes you read. Produce ONLY this session's platform output. NEVER open another binary.

Method

Locate via distinctive constants/strings in the body, cross-references from known callers/callees, or the owning class vtable (RTTI) if virtual. Verify by decompilation before committing to a candidate.

Mandatory self-check before emitting

The pipeline re-reads the bytes at your func_va and regenerates func_sig from them - a mismatch aborts the run. Therefore: read the real bytes via IDA MCP, derive the artifact FROM those bytes (wildcard relocated operands as ??), start at the TRUE function head, and only then write the YAML. A mismatch is always a bug in YOUR output.

Output schema (STRICT)

Write CFlattenedSerializers_CreateFieldChangedEventQueue.{platform}.yaml with EXACTLY these fields:

func_name: <TASK>
func_va: "<hex virtual address>"
func_rva: "<hex rva>"
func_size: "<hex size>"
func_sig: "<byte pattern, ?? wildcards, function head, minimal-unique>"

NEVER include vfunc_* or struct fields.

Verification

  1. Decompile and confirm the behavior matches the symbol's semantics.
  2. Uniqueness: the pattern must match exactly ONE location in the loaded binary.
  3. If no candidate can be confirmed, report the shortlist - a skipped symbol is safer than a wrong signature.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall