new-project

Invoke for /audit-diff, "audit this PR", "audit the diff", "pre-merge audit", "second opinion on this change", or any pre-PR independent review of a Python diff against the project's GUIDELINES.md / CLAUDE.md / DESIGN.md. Scaffold-aware delta from the harness-level audit-diff skill: knows this plugin's project-brief paths and ships the 11-dimension framework (with two-axis mode flags, primary-dim rule, drift sweeps, meta-principles) as a static spec plus per-dimension checklists, a surface-detection script, a coordinator brief, and a report template. The skill itself does NOT spawn agents; the model or user reading this skill drives orchestration using whatever dispatch mechanism the runtime provides. Required (per global rules §3) before merging any PR that touches business logic, schema, or production behavior; skip only for docs-only / dependabot grouped-minor / single-file typo PRs. Distinct from general code review: this is the structural pre-merge gate, not freeform feedback. Do NOT trigger on changelog edits ("normalize CHANGELOG" → changelog-normalizer), scaffolding requests ("new repo" / "spin up project" → new-project), or release-flow phrasings ("cut a release" / "ship vX.Y.Z" / "tag and push" → release-helper).

Invoke for any request to normalize, clean up, reformat, lint, fix, or check the style of a CHANGELOG.md file. Trigger on "normalize changelog", "fix changelog format", "clean up CHANGELOG entries", "check changelog style", "make the changelog consistent", "lint CHANGELOG.md", or `/changelog-normalize`. Use this — not freeform editing — whenever a CHANGELOG already exists and needs to conform to Keep-a-Changelog structure: canonical subheadings in spec order, commit/PR refs on every entry, no process narrative. Voice (imperative vs descriptive) is the author's choice — the skill validates structure and process-narrative content, not voice. Single responsibility: reformat existing entries. Does NOT invent, add, or remove changelog content. Skip for: writing release notes from scratch, summarizing commits into a new changelog, cutting a release / tagging a version / "release vX.Y.Z" / "ship X.Y.Z" (use `release-helper`, which composes this skill as its pre-step), or non-CHANGELOG markdown.

Invoke for /new-project or any request to create, start, scaffold, bootstrap, initialize, or spin up a new Python project or Python GitHub repository from scratch. Use this — not general coding — when the user wants a fresh Python repo that doesn't exist yet, with or without mentioning specific tooling. Automates GitHub repo creation, linting, testing, type checking, pre-commit hooks, and coverage in one step. Skip for: existing projects, non-Python languages, or questions about what templates contain.

Invoke for /release, "cut a release", "ship vX.Y.Z", "tag and push a release", "publish version X.Y.Z", or any request to perform the release sequence on an existing Python project that follows Keep-a-Changelog. Rotates [Unreleased] → versioned section, commits, annotated-tags, pushes, then bumps pyproject metadata to the next dev cycle. Use this — not ad-hoc git commands — whenever the user wants to release, even if they don't say "skill". For existing projects being released, not /new-project scaffolding. Skip for: non-Python projects without pyproject.toml, projects without a Keep-a-Changelog CHANGELOG.md, or pre-release / RC / alpha / beta tags (this skill handles final vX.Y.Z releases only).