- Add the config-health skill: a read-only monitor for hook wiring, rule references, and rule staleness; every mode exits 0.
- Ship its own SessionStart hook asset so installing the module registers the monitor; keep PreToolUse opt-in.
- Keep one install-state record per hook source, so hooks-runtime and config-health can share settings.json and uninstall removes both.
- Split the monitor into a CLI entry plus constants, paths, and scan modules; split scan_command and the hook contract suite. All files are under 800 lines and no function body reaches 50 lines.
Carry forward AbhiramMandala’s canonical TypeScript guidance from PR #3142, reviewed source head 643f61d604. Rebuild current-main counts, Pi projection and trigger digest without replacing existing registry entries.
Use bracket access under the documented noPropertyAccessFromIndexSignature baseline. Type-check and execute the actual fixture, compare published function bodies, and preserve deterministic undefined, sparse-array and concurrency regressions.
Validation: 26 focused checks; strict TypeScript compile; all repository validators; affected ESLint and Markdownlint; deterministic Pi rebuild; real npm pack; disposable Claude, Codex and Copilot install/repair/uninstall with exact skill bytes and preserved user files. Parent independently reviewed the complete staged diff.
Co-authored-by: AbhiramMandala <abhirammandala02@gmail.com>
Add a GitHub issue counterpart to the PR mode of /code-review. The
canonical workflow lives in skills/issue-review and walks nine phases:
fetch the issue with gh, build project context, classify type and
completeness, verify the claim against the code at HEAD, search for
duplicates and prior fixes, assess severity and decision, write a
review artifact with a draft reply, publish only on explicit flags,
and print a one-screen summary.
Issue text is treated as untrusted data: embedded instructions are
never followed, pasted code is never run, and arbitrary links are not
fetched. Writing to GitHub is opt-in via --comment or --label and the
workflow never closes, reopens, or assigns issues.
commands/issue-review.md is the thin slash-command shim. The new
structural test guards the frontmatter, required sections, phase
order, safety invariants, and registration on every surface.
Register the skill and command in package.json, agent.yaml, the
operator-workflows install module, the quick reference, the
command-agent map, and the README; regenerate the command registry
and sync catalog counts to 312 skills and 98 commands.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Tomoya.Fujita <fujita.tomoya@triorb.co.jp>
Add a skill for Platform Factory (pf), a daemonless deterministic OCI
builder with native SBOM/provenance, covering the detect/plan/freeze/
build/verify/run workflow and a companion Claude Code freeze-guard plugin.
Registered in package.json, install-modules.json, agent.yaml and the
skill-triggers manifest; catalog counts regenerated (311 -> 312).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claim from the verified payload and matched requirements in the
resource server's onAfterVerify hook, so a forged header can no longer
reserve a legitimate payment's key, and an invalid payment takes no
claim. Fail closed on a store error or timeout by returning an abort
(a throwing hook is skipped and would run the handler unguarded);
document fail-open as an explicit, idempotent-only choice. Cover
Permit2 (BigInt nonce) and keep claims until validBefore/deadline.
The test now drives the real @x402/express middleware with payments
signed by the real @x402/evm client and a stand-in facilitator that
checks EIP-3009 signatures with viem, so verification, the hook, the
handler and settlement run in their real order. Adds exact-pinned,
test-only devDependencies and refreshes the registry digest.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Integrate contributor PRs #3533, #3534, and #3535 on current main. Preserve the read-only module audit, canonical glossary and ADR ownership, and opt-in install closure. Refresh only the manual trigger manifest registry binding and coverage after adding the skill.
The compiled OpenCode tools import `tool` from `@opencode-ai/plugin/tool`
at module top level, and the hooks plugin imports those tools statically.
The package was only a devDependency, so production installs (OpenCode's
npm plugin cache, `npm install --omit=dev`) could not resolve it and the
whole plugin failed to load.
Move it to `dependencies` and add a build-opencode regression test that
fails when the built bundle imports a package not declared as a runtime
dependency.
Fixes#3543
(cherry picked from commit 106024070e)
Copy Grok installs from git archive of the marketplace pin, keep
per-server MCP attach on applyInstall, and make uninstall/rollback
own the managed version trees.
Ship .grok-plugin manifests so Grok can install ECC as a native plugin.
Resolve GROK_PLUGIN_ROOT and ~/.grok plugin homes so trusted hooks run.
Document trust/enable, ECC_HOOK_PROFILE, and root .mcp.json attachment.
- add skills/roundhouse-x402/ to package.json files and the
agentic-patterns install module (alongside agent-payment-x402)
- replace unused X402_FACILITATOR_* exports with an explicit
HTTPFacilitatorClient example for the upstream middleware
Terraform and OpenTofu patterns: project layout, version pinning, remote
state with locking, validated variables, secrets handling, for_each vs
count, moved/import refactoring, plan/apply CI workflow, and debugging.
Registered in package.json files, install-modules.json (platform module),
and the skill-triggers registry digest. Catalog counts synced (311 -> 312).
Resolved generated-file conflicts by taking upstream and re-running
catalog:sync, command-registry:write, and the trigger seeding.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Skills are listed individually in package.json files, so the new skills
were missing from the npm package.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Ship a finished vertical video to TikTok, YouTube Shorts and Instagram
Reels: file check with ffprobe, native metadata per platform, privacy and
disclosure choices, an approval gate, then publishing through whichever
path the user already has (a connected publishing MCP server, the official
APIs, or a manual upload sheet), and links read back from each platform.
Fills the gap between the media-generation skills (remotion, manim,
video-editing, videodb) and social-distribution (crosspost is text-only).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>