Review or update GitHub repository hardening guidance and its Terraform implementation under config/infra, including rulesets, required checks, scanning, permissions, provider pins, and plan/apply safety. Do not use for ordinary app code, generic template adaptation, release integrity, or routine workflow validation.
Draft a concise pull request handoff after substantive repository changes are finished or ready for review. Trigger when wrapping up code, test, script, workflow, release, security, documentation-with-behavior-impact, or template customization changes and the user needs a PR title/body grounded in the real diff…
Use when reviewing or improving this template's release-integrity story, including artifact verification, SBOMs, attestations, vulnerability scanning, signing guidance, and release-workflow safety. Do not use for general CI validation, GitHub-settings-only work, or unrelated template customization.
Adapt the template to project code, language and framework needs, or optional Go, Node.js, SQL, and polyglot guidance. Covers dependencies, runtime behavior, Docker, Makefile targets, and customization surfaces. Do not use for routine bug fixes, pure workflow validation, GitHub hardening, or release-integrity-only…
Manual-only skill. Use ONLY when the user explicitly invokes: $security-review (Codex) or /security-review (Claude Code) Never select this skill via semantic matching.
Use when validating repository workflows after changes to Docker-first Makefile targets, Dockerfiles, scripts, CI, release packaging, smoke tests, or documentation alignment. Do not use for repo redesign, GitHub-policy-only changes, or instruction-only skill edits with no workflow impact.
★not rated 9 8d agoA57 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: