Review whether a feature is genuinely "done" against the project Definition of Done — plan exists, correct branch, fmt/lint/check/architecture/tests all green, and security & legal compliance (ASVS/GDPR) cleared — running the root make gates (with per-service fallback) plus the security review, auto-fixing only…
Author an executable, phased implementation plan under docs/plans — first gather real context from the repo and docs, debate the ambiguities, trade-offs and open decisions with the human, and only after explicit human confirmation write the plan. Produces Master Plans (a directory with a bootstrap entry point, master…
@file .claude/skills/pr-check-release/SKILL.md @description Executable form of the "Feature → dev via PR" step: verifies a work branch (all gates + mergeability into dev), then pushes it and opens/updates a well-formed PR to dev (title, description, assignee, labels). @layer agents @created Platform Team -->.
Merge the current branch's open PR into dev on GitHub — verifies CI is green and no conflicts exist, merges via gh, deletes the remote branch, then cleans up locally (switch to dev, pull, delete local branch). Use when the PR is open and all checks have passed and you want to land it.
Review whether dev is healthy and ready to be promoted to main (production) — the human release gate from the Release & Deploy process. Surfaces the exact set of changes being promoted (main..dev), checks CI/gate health on dev, confirms no in-flight [WIP] PRs are being left behind, and reports merged-branch cleanup …
★not rated 5 1mo agoA132 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: