Skip to content

tsunami28/MindNova / .claude/skills/create-run-gates

create-run-gates

Verified

Run all the CI code-analysis gates locally against a change, before opening a PR, so failures are caught in seconds instead of after a full pipeline cycle. Use when the user says "run the gates", "check before I push", "will CI pass", "run the CI checks locally", "did I break a gate", or "pre-PR check", or as the verification step at the end of a change. Do NOT use to evaluate a skill's quality (that is governance-validate-skills) or to validate only the artifact graph and docs wiki (that is governance-check-graph); this runs the whole gate set the pipeline runs.

Run Gates

Usable by any persona, typically Developer or QE. Invoked as /create-run-gates.

Run the same gates the code-analysis-pipeline.yml runs, on the working tree, so a doc, skill, graph, or house-style violation is found and fixed locally instead of failing CI after a PR is open. This is the sibling of create-verify-test-coverage: that one verifies tests and coverage, this one verifies the gates.

Run it

pwsh MindNova/toolsInvoke-LocalGates.ps1
  • Add -IncludeToolTests to also run the gate scripts' own Pester tests.
  • Add -CoverageFile <merged opencover xml> to include the C09 coverage gate (needs a test run first).
  • The script exits non-zero if any BLOCKING gate fails, so it doubles as a scriptable pre-push check.

Reading the result

Each gate is Blocking or Advisory:

  • Blocking (docs line-citations C02, artifact graph, docs wiki + index C10, em-dash C11, skill hygiene, story-trait malformed keys): a failure fails CI. Fix before the PR.
  • Advisory (LogMindNova C05, KQL escaping C04, PascalCase wire names C06, coverage C09): reported as findings, not yet blocking (pre-existing debt is being cleared). Do not add NEW advisory findings on changed code.

The summary table marks each PASS / FAIL / ADVISORY; the run exits non-zero only on a blocking FAIL.

Enforce it on every push (optional, recommended)

A git pre-push hook runs the blocking gates automatically on git push, from any tool (terminal, Claude Code, Copilot), because it is a git hook, not an agent feature. Enable once per clone:

git config core.hooksPath .githooks

Or run pwsh MindNova/toolsInstall-GitHooks.ps1 once, which sets that config and checks for pwsh. Bypass intentionally with git push --no-verify. Needs pwsh on PATH; if absent the hook warns and allows the push rather than blocking on a tooling gap.

Next steps

  • /create-verify-test-coverage (QE) - verify tests and coverage alongside the gates before the PR.
  • If a blocking gate fails, fix the listed issue and re-run; the gate output names the file and rule.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall