clm

Resolve a GitHub issue in the CLM repo end-to-end: investigate the issue thread and code, reproduce the problem, name the root cause, design and implement a fix with regression tests that fail before the fix, optionally run an adversarial review, and ship a PR that closes the issue. Use when asked to fix / resolve / investigate-and-fix issue #NNN. Args: the issue number, optionally followed by --review (force an adversarial review) or --no-review (skip it); with neither flag, decide via the risk heuristic in this skill after the diff exists.

Cut a release of the CLM PACKAGE to PyPI (bump the version, publish coding-academy-lecture-manager). Use when asked to release/publish CLM, bump its version (patch/minor/major), or ship a new clm version to PyPI. This is the PYTHON PACKAGE release, NOT publishing course content to a cohort (that is course-release). Publishing is AUTOMATED — landing a `Bump version …` commit on master (via merge commit) triggers .github/workflows/release.yml, which gates on CI-green then publishes via OIDC and creates the GitHub Release. Your job is docs + CHANGELOG + version bump; never run `uv publish` / `gh release create` by hand. Source of truth: docs/developer-guide/releasing.md.

Ship a finished change in the CLM repo as a PR, the autonomous way: branch → commit → push (fast-suite gate) → PR → CI-gated auto-merge. Use when a feature/fix/docs change is complete and ready to land, especially from a git worktree. Encodes the CLM-specific landmines: a worktree must NEVER switch to literal master (reset its OWN branch off origin/master); commit/PR trailers; changelog goes in changelog.d/ NOT the CHANGELOG [Unreleased] section; update the matching `clm info` topic for any CLI/spec/behavior change; the pre-push hook runs the fast suite (cap xdist workers to dodge contention flakes); never edit files during a backgrounded push; auto-merge is CI-gated; open a PR fresh off master (don't stack) to avoid the retarget-no-CI gap.