development_skill_audit #215

Open
delandtj wants to merge 0 commits from development_skill_audit into development
Member
No description provided.
New tool at tools/skill_audit/ that extracts structured "claims" from
SKILL.md, howto/, and prompts/ via claude -p (Haiku 4.5), clusters
them deterministically (exact-key + token-overlap with Jaccard
filter), and adjudicates candidate pairs (Haiku, escalating to
Sonnet 4.6 on contradict / low confidence).

First-run findings committed to claude/skills/_meta/:
- 12 contradictions, including the rust_toolchain forbid vs
  cargo_deps example, a merge-strategy clash between
  code_manage_development_branch and forge_workflow, a CI trigger
  clash between forge_ci and forge_package, and a 0o770 vs 0660
  socket-permission triple.
- 15 orphan references including the 4 known hero_proc_log refs
  left over from the rename to hero_log.
- 78 refine-relationships surfaced for review.

Cache (tools/skill_audit/.cache/) is gitignored; the audit reads
content-hashed extract and adjudicate caches so re-runs after
touching one SKILL.md only re-extract that file.

ADR: see /home/delandtj/.claude/plans/i-was-wondering-how-rippling-sifakis.md
(also mirrored into codebase-memory-mcp under
home-delandtj-prppl-hero_skills).
The runtime dependency surface was implicit -- "Auth and cost" mentioned
OAuth in passing but never said the tool actually requires the claude
CLI on PATH or a minimum nushell version. Made it a Prerequisites
section so a fresh checkout knows what to install.
Resolves 11 of 12 high-confidence contradictions and 5 orphan references
flagged in claude/skills/_meta/conflicts.md by the 2026-05-05 audit run.

- rust-version cluster (5 contradictions collapse): harmonize MSRV to "1.94"
  in cargo_deps, hero_rust_repo_create, herolib_import, rust_toolchain.
  rust_toolchain now mandates rust-version = "1.94" (was: forbid the field).
  dioxus prerequisite reworded to defer to rust_toolchain.
  rust-toolchain.toml channel bumped 1.93.0 -> 1.94.
- merge strategy: code_manage_development_branch now squash-merges feature
  commits into development per hero_branching (was: merge commit).
- socket permissions: hero_crates_best_practices_check 0o770 -> 0o660 to
  match hero_sockets default (also consistent with herolib_openrpc_authorize).
- CI triggers: forge_ci test.yaml triggers harmonized to branches: ["**"]
  to match the live my_init/.forgejo/workflows/test.yaml ground truth and
  the explicit "every push to any branch" policy in forge_package.
  forge_package itself: ["*"] -> ["**"] for glob-correctness.
- hero_proc_log -> hero_log rename: 4 frontmatter related: refs and 1
  inline reference updated across hero_proc_service_{selfstart,singlebin},
  hero_proc_openrpc, hero_proc_sdk_jobs_use.
- hero_context.related: replaced 3 made-up topic names (hero_proc, openrpc,
  uds_http) with real skill ids (hero_proc_sdk, herolib_openrpc, hero_sockets,
  hero_claim_format).

Not addressed in this commit:
- Inline orphan refs to skills that don't exist (archipelagos, version_sync,
  tests_playwright, hero_release) -- needs decision on whether to author the
  skill or rewrite the reference inline.
- The dioxus_bootstrap _ui_wasm vs hero_crates_best_practices_check suffix
  closure contradiction -- needs a policy call on whether _ui_wasm is a
  valid extra suffix or whether dioxus_bootstrap should drop the suffix.
- The repo_check vs prompts/multi_action_ui_repos.md "make run" overlap
  (build-and-run vs install-then-binary-only) -- prompts/ files are out of
  scope of the skills surface; punt to a separate review.
- hero_rust_repo_create's audit-flagged empty related: is a parser false
  positive on multi-line YAML lists; tracked for skill_audit v2.
The skill_audit pipeline writes directives.json + conflicts.md to
claude/skills/_meta/. The CI validator was treating that as a
malformed skill (missing SKILL.md) and failing the workflow.

Skip leading-underscore and leading-dot directories — Unix convention
for non-skill scratch storage.
docs(skill_audit): rerun audit, refresh claude/skills/_meta/
All checks were successful
Build and Publish Skills / build-and-publish (pull_request) Successful in 4s
3ec1260106
Pipeline at tools/skill_audit/, results at claude/skills/_meta/.
docs(skill_audit): explain why conflicting skill claims hurt the LLM
All checks were successful
Build and Publish Skills / build-and-publish (pull_request) Successful in 3s
9e2419fcb8
Add claude/skills/_meta/README.md so the audit output dir is
self-documenting -- why contradictions and orphan refs in skills
silently corrupt model output, and how to read conflicts.md.
mik-tf added this to the ACTIVE project 2026-05-06 17:32:03 +00:00
All checks were successful
Build and Publish Skills / build-and-publish (pull_request) Successful in 3s
This pull request has changes conflicting with the target branch.
  • claude/skills/cargo_deps/SKILL.md
  • claude/skills/forge_ci/SKILL.md
  • claude/skills/hero_proc_sdk_jobs_use/SKILL.md
  • claude/skills/hero_proc_service_selfstart/SKILL.md
  • claude/skills/hero_proc_service_singlebin/SKILL.md
  • claude/skills/hero_rust_repo_create/SKILL.md
  • claude/skills/rust_toolchain/SKILL.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin development_skill_audit:development_skill_audit
git switch development_skill_audit

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch development
git merge --no-ff development_skill_audit
git switch development_skill_audit
git rebase development
git switch development
git merge --ff-only development_skill_audit
git switch development_skill_audit
git rebase development
git switch development
git merge --no-ff development_skill_audit
git switch development
git merge --squash development_skill_audit
git switch development
git merge --ff-only development_skill_audit
git switch development
git merge development_skill_audit
git push origin development
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_skills!215
No description provided.