3 Commits

Author	SHA1	Message	Date
BERORINPO	db7f2a6fd5	fix(skills): move top-level origin frontmatter key under metadata ... The official Agent Skills spec (agentskills.io/specification) whitelists exactly 6 top-level frontmatter keys (name/description/license/compatibility/metadata/ allowed-tools). A top-level `origin` key fails the official validator (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate). This moves `origin: X` -> `metadata.origin: X` across the canonical skills/ tree, preserving each value verbatim. Frontmatter-only, minimal diff. - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata) - origin values preserved verbatim (verified 251/251) - YAML validated on all changed files - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors .cursor/.kiro/.agents left untouched; presumably regenerated from canonical) Addresses #2233	2026-06-11 21:12:21 +09:00
Affaan Mustafa	e755c5f72b	fix: make plugin hooks run on Node 21+ and green the suite under modern Node (#2184) ... ROOT CAUSE: hooks load plugin-hook-bootstrap.js via `node -e "...; process.argv.splice(1,0,s); require(s)"`. On Node 21+, require.main is `undefined` under --eval, so the `if (require.main === module)` guard was false and main() never ran — every plugin hook silently no-op'd (e.g. the MCP-health PreToolUse hook stopped blocking). CI (Node 18/20) hid this; it only surfaces on Node 21+. Fix: also run main() when require.main is undefined (the eval-bootstrap case), while staying dormant on real imports. Also clears pre-existing main debt the full local suite enforces: - catalog:sync — README/docs agent+skill counts drifted after recent merges - tests/ci/supply-chain-watch-workflow: update checkout SHA to the merged v6.0.3 (#2183) - markdownlint + check-unicode-safety --write across docs/skills Suite: 2683/2683 green under Node v25; lint + unicode clean. Co-authored-by: ECC Test <ecc@example.test>	2026-06-07 16:05:28 +08:00
linsy	28b78dd7bf	feat: add inherit-legacy-style — prevent AI code style drift in legac… (#2098) ... * feat: add inherit-legacy-style — prevent AI code style drift in legacy projects - 4-dimension meta-architecture scan (File Anatomy, State & Control Flow, Infrastructure, Error Handling) - Scale-adaptive (small=full read, large=smart sampling) - Signal-threshold noise reduction with one-at-a-time grilling protocol - Generates .ai-style-rules.md with persistent CLAUDE.md hook - Language- and framework-agnostic * fix: add AskUserQuestion to allowed-tools, add When to Use/How It Works/Examples sections per bot review --------- Co-authored-by: wulinzai <linsywu@gmail.com>	2026-06-07 13:26:40 +08:00