Skip to content
cccskills
FreePublished on GitHub

hotfix-backport

Backport fixes from main onto release/YYYY.WW in the ai repo with cherry-pick and rebase merge so release-please changelogs stay correct. Use when hotfixing a release branch, cherry-picking to release/*, or preparing a release backport PR.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Hotfix backport to release/*

Workflow

  1. Identify commits on main to backport (merge commits or PR numbers).
  2. Branch from the target release branch:
    git fetch origin main release/YYYY.WW
    git checkout -b hotfix/UN-XXXXX origin/release/YYYY.WW
    
  3. Cherry-pick in order (oldest first):
    git cherry-pick <sha1> <sha2> ...
    
  4. Open a PR targeting release/YYYY.WW with a list of backported commits/PRs in the description.
  5. Merge with Rebase and merge only (squash is blocked by branch rules).

CI guardrails

  • .github/scripts/check-release-lineage.sh — each PR commit must be on main or patch-equivalent (git cherry - prefix). Cherry-picks get new SHAs; identical hashes are not required. No commit-metadata bypass (author/subject are forgeable).
  • release-please--* PRs skip lineage in ci.yaml (automation-owned version/changelog bumps).
  • Do not squash-merge: one squashed commit breaks release-please changelog generation.

After the fix PR merges

release-please opens chore: hotfix release/YYYY.WW to YYYY.WW.N. Approve and rebase-merge that PR too. PyPI publish follows the GitHub Release event.

Related

  • release-process — versioning and changelog ownership
  • git-conventional-commits — commit subjects on cherry-picked commits must stay conventional
  • model-deployment LESSONS-LEARNED — monorepo pins after AI packages ship

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Implement comprehensive error handling for Python code paths to keep services resilient and user-friendly. Use when failures are currently silent or exceptions leak through.

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

Tabular and numerical data analysis with descriptive statistics and insights. Use when the user provides data, tables, CSVs, or numbers and wants analysis.

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

Financial factsheet analysis with key metrics extraction and investment rationale

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

ci-fix

Free

Diagnose and fix CI failures without leaving your editor.

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

Reproduce ai-repo PR checks locally with Poe and CI scripts, including per-package typecheck and coverage behavior. Use when validating changes before push or when user asks which local commands match CI.

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

Ask clarifying questions before implementing to ensure Python requirements are understood. Use when a task lacks detail, dependencies are unclear, or multiple interpretations are possible.

The English summary is being prepared. Showing the original description.

Unique-AG/ai5Updated Oct 20, 2026

See all skills by Unique-AG

Report a problem with this skill