Add deps.txt maintenance guide and WASM CI patterns to skills #18

New issue

Closed

opened 2026-02-17 19:24:34 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-02-17 19:24:34 +00:00

Owner

Context

During CI fixes on hero_books (PR #57) and hero_archipelagos (PR #14), we discovered recurring patterns that are not yet documented in the skills. hero_books CI broke because deps.txt referenced a crate that had migrated to a different repo (herolib_osis → hero_rpc_osis). hero_archipelagos CI had 130 consecutive failures partly due to fragile wasm-pack path listings and a package name hyphen/underscore mismatch.

Goals

Add deps.txt maintenance rules to forge_ci skill (what to update after dependency migrations)
Add WASM compilation strategy guidance to forge_ci (cargo check vs wasm-pack)
Add new CI issue rows: stale deps.txt, package name mismatches, stale generated code
Add deps.txt sync checklist to hero_coderoot skill
Document the deps.txt file format and how CI uses it

## Context During CI fixes on hero_books (PR #57) and hero_archipelagos (PR #14), we discovered recurring patterns that are not yet documented in the skills. hero_books CI broke because deps.txt referenced a crate that had migrated to a different repo (herolib_osis → hero_rpc_osis). hero_archipelagos CI had 130 consecutive failures partly due to fragile wasm-pack path listings and a package name hyphen/underscore mismatch. ## Goals - Add deps.txt maintenance rules to `forge_ci` skill (what to update after dependency migrations) - Add WASM compilation strategy guidance to `forge_ci` (cargo check vs wasm-pack) - Add new CI issue rows: stale deps.txt, package name mismatches, stale generated code - Add deps.txt sync checklist to `hero_coderoot` skill - Document the deps.txt file format and how CI uses it