pre-push-release-automation

Pre-Push Release Automation

Overview

Run the full release loop with minimal back-and-forth: local checks, scoped formatting, commit, push, CI monitoring, Release Please PR handling, post-merge verification, and final repository synchronization.

This skill is optimized for Roo Code sessions where the user explicitly asks to push and merge the auto-release PR if checks pass.

When to Use

Use this skill when the user asks for any of these:

• “final pre-push check”
• “lint, prettify, pass, then push”
• “push to git”
• “merge the auto-release PR if CI/CD passes”
• “run release please and publish”
• “verify CI after merge”

Preconditions

• Confirm the repository is a Git working tree.
• Confirm the intended branch and remote with git status --short --branch and git remote -v.
• Never include unrelated user changes unless explicitly requested.
• Do not manually edit release-generated files such as CHANGELOG.md, .release-please-manifest.json, package.json, or lockfiles unless the current task specifically requires release metadata changes. Let Release Please own release-note and version bumps.

Standard Flow

1. Inspect repository state

Run:

git status --short --branch
git remote -v

If unexpected deleted or modified files appear, pause and determine whether they are related. Restore unrelated changes before committing unless the user explicitly wants them included.

2. Run local checks

Prefer the project’s native commands. For this Node/npm project pattern:

npm run format
npm run test
npm run lint
npm run format:check

If full format touches release-generated or unrelated files, restore those unrelated files and run targeted checks on the intended files instead:

git restore -- CHANGELOG.md
npm run test
npm run lint
npx prettier --check <changed-files>

3. Review the diff and scan for secrets

Run:

git status --short
git diff --stat
git diff -- . | grep -iE 'password|secret|api[_-]?key|token' || true