Skip to content

Clean up .claude config: fix broken paths, dedupe tool docs, sync livetools skill#18

Merged
Night1099 merged 3 commits into
masterfrom
claude-config-cleanup
Jun 11, 2026
Merged

Clean up .claude config: fix broken paths, dedupe tool docs, sync livetools skill#18
Night1099 merged 3 commits into
masterfrom
claude-config-cleanup

Conversation

@Night1099

@Night1099 Night1099 commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

Audit fixes for the .claude/ configuration — one real bug, several doc-drift issues, dedup of tool lists — plus a full sync of the parallel .cursor, .kiro, and .github instruction trees per the CODE_REVIEW.md checklist.

Commit 1 — .claude cleanup

Bug fixes

  • static-analyzer agent had a broken path: its setup step pointed at .claude/rules/tool-catalog.md; the catalog lives at .claude/references/tool-catalog.md.
  • dynamic-analysis skill had drifted behind livetools: dipcnt, memwatch, vishook, gamectl, and mem alloc exist in the CLI but were missing from the skill. Added quick-reference and command-detail sections written from the actual argparse definitions.

Dedup (single source of truth per list)

  • Inline-exception allowlist: lives only in tool-dispatch.md "Run Directly" (now includes the previously missing pyghidra_backend.py status); CLAUDE.md states the rule and points there.
  • DX analysis script table: lives only in tool-catalog.md; tool-dispatch carries a pointer.
  • livetools syntax: canonical in the dynamic-analysis skill; tool-dispatch and tool-catalog point at it.
  • Auto-loaded session context drops from ~2,280 to ~2,130 words while gaining content.

Skill description hygiene

Both skill descriptions are now trigger-only ('Use when...') with no workflow summary.

Settings

  • New shared .claude/settings.json permission allowlist covering the documented inline workflows.
  • settings.local.json untracked and gitignored; its git permissions migrated into the shared file.

Commit 2 — IDE tree sync (CODE_REVIEW.md checklist)

  • Same broken-path bug fixed in two more places: .kiro and .github static-analyzer agents pointed at the nonexistent .claude/rules/tool-catalog.md; they now point at their own tree's catalog.
  • Back-ported improvements that only existed in .cursor/.kiro into the canonical .claude dynamic-analysis skill: hook-address verification recipe, ASLR rebasing guidance, "hook the game's CALL instruction, not the DLL function" and "zero hits = diagnose, don't give up" patterns, and the Anti-Patterns section.
  • Propagated canonical skill bodies (dynamic-analysis, dx9-ffp-port) to .cursor/skills, .kiro/powers, and .github/skills, preserving each tree's frontmatter format. The dx9-ffp-port copies predated the template-copy workflow entirely (described editing rtx_remix_tools/dx/remix-comp-proxy/ directly).
  • Added the missing livetools commands (vishook, gamectl, mem alloc) to all IDE tool catalogs and decision guides.
  • Rebuilt the .github tool catalog from current content — it predated the pyghidra backend entirely (no dual-backend section, no dataflow inline commands).
  • Fixed stale facts verified against code: diagnostics log is rtx_comp/diagnostics.log (10 references said ffp_proxy.log); the INI template lives in assets/.

…etools skill

- Fix static-analyzer agent pointing at .claude/rules/tool-catalog.md
  (actual location is .claude/references/tool-catalog.md)
- Add missing livetools commands to the dynamic-analysis skill:
  dipcnt, memwatch, vishook, gamectl, mem alloc
- Make each tool list single-source: inline allowlist lives in
  tool-dispatch.md, DX script table in tool-catalog.md, livetools
  syntax in the dynamic-analysis skill; other docs point instead of copy
- Rewrite both skill descriptions as trigger-only (no workflow summary)
- Add shared .claude/settings.json permission allowlist; untrack and
  gitignore settings.local.json
Apply the .claude config fixes to the parallel .cursor, .kiro, and
.github instruction trees, and back-port improvements that only
existed there:

- Fix broken tool-catalog path in .kiro and .github static-analyzer
  agents (pointed at nonexistent .claude/rules/tool-catalog.md; now
  point at their own tree's catalog)
- Back-port into the canonical .claude dynamic-analysis skill:
  hook-address verification recipe, address rebasing guidance,
  'hook the game's CALL, not the DLL function' and 'zero hits =
  diagnose' patterns, and the Anti-Patterns section
- Propagate the canonical skill bodies (dynamic-analysis,
  dx9-ffp-port) to .cursor skills, .kiro powers, and .github skills;
  the dx9-ffp-port copies predated the template-copy workflow
- Add missing livetools commands (vishook, gamectl, mem alloc) to all
  IDE tool catalogs and decision guides
- Rebuild the .github tool catalog from the current content (it
  predated the pyghidra backend entirely)
- Fix stale ffp_proxy.log references (actual path is
  rtx_comp/diagnostics.log) and note the INI lives in assets/
…threshold

Review fixes for this PR:

- Back-port content the dx9-ffp-port sync deleted from the .cursor/.kiro/
  .github copies without first folding it into the canonical .claude skill:
  the "Skinning Stability: Finding Game-Specific Hook Points" workflow, the
  "Bones mixed up between NPCs" pitfall, and the stages 1-7 disabling detail
  (verified against ffp_state.cpp). Propagated to all four trees; bodies
  remain identical across trees.
- Note in all four dynamic-analysis skills that vishook --threshold is
  parsed as hex (agent.js parseInt(..., 16)): default 500000 = 0x500000.
- Update .github dx9-ffp-port frontmatter description to the trigger-style
  wording used by the other trees.
@Night1099 Night1099 force-pushed the claude-config-cleanup branch from d9323f7 to 2bee974 Compare June 11, 2026 05:03
@Night1099 Night1099 merged commit d73347a into master Jun 11, 2026
2 checks passed
@Night1099 Night1099 deleted the claude-config-cleanup branch June 11, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant