rom24-quickmud-python

Write the end-of-session deliverables for QuickMUD ROM-parity work — generate docs/sessions/SESSION_SUMMARY_<date>_<topic>.md and refresh docs/sessions/SESSION_STATUS.md from the session's git diff and trackers touched. Use when the user says "wrap up", "write the session summary", "session handoff", at end of a parity audit, or after rom-gap-closer batches. Follows the AGENTS.md "Session Notes" conventions exactly.

Automates the creation of GitHub releases using the GitHub CLI (gh)

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Run a completeness sweep on ONE ROM↔Python divergence class (async-delivery, RNG, equipment-key, pointer-identity, signed-math, ordering, …) and route it to its correct verification layer. Use when measuring "how close to done" on a known class, validating that a class is clean, or converting a hand-verified contract into a self-maintaining guard. Encodes the convergence-probe + recall-oracle + layer-routing method. Status lives in docs/parity/DIVERGENCE_CLASS_ROSTER.md; this skill produces a guard test (Layer A), a domain-read note (Layer B), or a diff_harness scenario (Layer C) — never a bare ✅ in an instruction file. NOT a replacement for cross-INV probe-then-scope, rom-gap-closer, or rom-parity-audit — it points work INTO them.

Close a single ROM parity gap by ID (e.g. DROP-001, ENTER-002, GET-013, HANDLER-014, QUAFF-001). Use when the user names a specific gap to fix, or when working through gaps from a docs/parity/<FILE>_C_AUDIT.md audit. Runs the standard TDD close flow: locate ROM C lines, locate Python entry point, gitnexus_impact upstream, write a failing integration test in tests/integration/, implement the fix in mud/, update the audit doc row to FIXED, add a CHANGELOG entry, and produce a single feat(parity) or fix(parity) commit. Not for bulk audits — use rom-parity-audit for those.

Run a full ROM 2.4b6 → Python parity audit on a single ROM C source file (e.g. act_obj.c, scan.c, special.c). Use when starting a new file-level audit, when the user says "audit X.c", or when ROM_C_SUBSYSTEM_AUDIT_TRACKER.md shows a P0/P1 file as Partial/Not Audited. Encodes the 5-phase methodology: (1) read ROM C and Python entry point, (2) write per-file audit doc with gap table, (3) ID gaps with stable IDs (FILE-001 etc.), (4) close gaps via integration tests + implementation (defer to rom-gap-closer per gap), (5) flip tracker rows and write a session summary. Not for single-gap closures — use rom-gap-closer for those.