Adds a rails-security skill covering production configuration,
authentication and session rotation, authorization, strong parameters,
SQL injection, XSS and output escaping, CSRF, file uploads, API security,
credentials, untrusted boundaries, and dependency scanning.
Fills the Rails gap alongside the existing laravel-security, django-security,
and springboot-security framework skills. Defers decisions to
rules/ruby/security.md and focuses on the how, per the rules-vs-skills split.
Registers skills/rails-security in the framework-language install module,
agent.yaml, the package.json files list, the ruby entry in
config/project-stack-mappings.json, and the plugin and marketplace manifests.
Adds the reciprocal skill reference to rules/ruby/security.md, matching how
the python, php, and java security rules point at their framework skills.
Updates the catalog count to 294 across the documented surfaces, and bumps
registryDigest and coverage.skills in the skill-triggers context pack by hand:
scripts/dev/generate-skill-triggers.js requires Codex auth to regenerate, and
no new triggers are introduced, so triggersDigest is unchanged.
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>
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.
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>
Adds godot-patterns and godot-testing to agent.yaml and the
framework-language install module, lists gdscript-reviewer in AGENTS.md,
syncs catalog counts (72 agents, 304 skills), and hand-seeds skill triggers.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Preserve full contributor head; refresh catalogs and Pi projection. Verify disposable Claude/Codex installs and resource discovery, with no automatic hooks or governance files.
pi/core and the bundled blueprint skill now refer to the project as ECC only;
the generated README no longer expands the name. Profile contents, package
name and paths are unchanged (123 skills, 24 commands).
The release workflows poll npm for up to five minutes after publish before
verifying the artifact. In 2.2.2 the check gave up after about 30 seconds while
npm was still processing, failing the run before latest was promoted and the
GitHub Release was created.
Version metadata synced to 2.2.3 with CHANGELOG, translated release headings
and release notes; skill-triggers registryDigest updated for the blueprint text.
The conflicts were all counter bumps. Upstream moved 286 -> 292 skills while
staying at 94 command shims; this branch adds one of each, so the merged values
are 293 skills and 95 shims, carried across the English, Turkish and Chinese
docs. Upstream's 2.2.2 version is kept.
One line needed care and nearly went wrong: the v2.0.0 changelog entry records
"281 skills, 67 agents, 94 command shims". That 94 is a fact about a past
release, not a live counter, and a blanket substitution had rewritten it. It is
back to 94. The Discord snowflake and the Perl badge colour both contain "94"
too and are untouched.
While here, the pin was stale. It named 0.7.0, three minor versions behind, so
anyone installing through this skill got a tool without Gemini support, the
read-only doctor report, PNG export or the portable ledger. Raised to 0.10.0 —
knowingly, which is what the skill's own note asks for — and the documented
`npm view @tokenchit/cli@0.10.0 dist.integrity dist.tarball` was run to confirm
it resolves.
The agent list was stale for the same reason: Gemini CLI became a real adapter
in 0.9.0 and the skill still advertised three agents. Verified against the
published 0.10.0 tarball rather than from memory — `init --help` and `doctor`
both name Claude Code, Codex, Gemini CLI and OpenCode.