Use for commit-and-publish, push, pull request creation or follow-up, merge, version bump, plugin release, or issue delivery in supported MoviePilot repositories. Uses fork-based upstream contribution rules for jxxghp targets.
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
Create or update a releases.json manifest so registries and agents can find where a company or project publishes its release notes. Use this whenever someone wants to "list our product on Releases", "add a releases.json", "get indexed on releases.sh", "here's our website, make us a manifest", declare a changelog /…
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
Create a new release of tmux-scout-golang. Use this skill whenever the user asks to cut a release, create a new version, bump the version, tag a release, or ship a new version of this project.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — /dev-flow start scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; /dev-flow ship validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a…
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
Use when releasing this repository from the CLI by promoting develop to main with a fast-forward push, grading the release as patch/minor/major by what installed projects actually pay, computing the next version from the latest tag, and publishing a GitHub release with agent-written notes. No release PR, no…
Automate the creation of high-quality project showcases: UI captures, security scans, repo health audits, README injection, GitHub releases, and social media launches.
Use when publishing a new GitHub release of a Titanium native module — covers researching the repo's historical release tag / name / notes convention, rebuilding the module from the merged default branch, and uploading the produced .zip per platform. Triggers include "create a release", "cut a release", "tag a…
Automate semantic version releases across project types by detecting version files, bumping versions, updating changelogs, creating git tags, and optionally publishing GitHub releases. Use when users ask to cut a release, bump the version, prepare a new version, tag a release, update the changelog for a release, or…
When a change is finished and you're ready to commit, push, or release. The final gate that makes sure you ship working, safe code — and that project memory is updated so the next session inherits your work.
Use when a Noah task affects GitHub Actions workflows, CI checks, deployment automation, VPS provisioning, production env rendering, release pipeline safety, or operational secrets for build and deploy.
Manages version control using jujutsu (jj) instead of git. Provides workflows for creating changes, describing commits, pushing to remotes, and managing bookmarks. Use when performing any version control operation, when the user mentions commits, diffs, branches, push, pull, or history, or when git commands would…
Use when a reviewed pull request is about to be merged, including digest this PR before I merge, should I merge this, or merge this PR. Briefs merge, debug, or do not merge plus numbered live options and waits for a numbered reply. Option 1 is Proceed to merge. A bare merge request still runs this review and still…
Use when deploying to production, releasing a version, shipping to users, going live, or rolling back a deployment. Also handles deployment failures and health checks.
A release checklist for publishing updates to the claude-code-harness plugin repository. It covers deciding whether a Git tag is needed, updating plugin versions, recording the change, staging files, publishing, and checking that the remote repository is synchronized.
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: