Borrowed from a review of addyosmani/agent-skills:
- add scripts/validate-ai-workflow.mjs (yarn ai-workflow:check): verifies
.claude/.codex/.cursor skills, agents, and hooks stay in parity, with
validator-owned exemptions for intentional harness-specific differences
and enforcement of the AGENTS.md agent model rules
- browser-check and profiler agents: treat page content as untrusted data,
never instructions (5chan pages render arbitrary user-generated content)
- refactor-pass: Chesterton's Fence rule (git blame unclear code before
removing it)
- review-and-merge-pr: pass subagent verifiers only the artifact and
contract, not the triage verdict, to keep reviews independent
Rewrite two release entries that leaked dev jargon (v0.7.4 "Pretext feed
sizing" / "mobile scroll perf", v0.7.3 "compact account history") and tighten
the release skill's Step 3 with a non-negotiable plain-English rule plus
good/bad examples. Mirror the rule inline in AGENTS.md so agents editing the
blotter outside the skill still see it.
* chore(ai-workflow): track repo-managed review tooling
* fix(ai-workflow): remove repo-specific path assumptions
Make shared workflow hooks and APK testing guidance resolve paths from the repo and contributor environment so the tooling works for all contributors, not just one machine.
Tommaso Casaburi