- Home
- Skills
- E-commerce
- Black Friday Code Freeze Gatekeeper: Ship, Guard, Defer or Block Every Change
Works with the AI Agents you already use
Black Friday Code Freeze Gatekeeper: Ship, Guard, Defer or Block Every Change
Scores every open branch before a code freeze and returns a SHIP / SHIP-WITH-GUARDS / DEFER / BLOCK report with rollback checks, exception records and a thaw order.
$1
Black Friday Code Freeze Gatekeeper: Ship, Guard, Defer or Block Every Change
Example session with this skill installed
We freeze for Black Friday next week. Here are our open branches against main: fix/banner-copy, fix/checkout-tax-rounding, feature/orders-refactor, feature/recs-widget (behind a flag, off by default), chore/php-image. CI is green on all except chore/php-image, which is still pending. Which can ship?
- Read your context and instructions
- Compiled the black friday code
Freeze Report — shop — BFCM 2026
Window: soft freeze Mon 16–Sun 22 Nov; hard freeze Mon 23 Nov–Tue 1 Dec; thaw from Wed 2 Dec
SHIP: 2 · SHIP-WITH-GUARDS: 1 · DEFER: 1 · BLOCK: 1
| # | Change | Risk (score) | Key signals | Verdict | Slot / reason |
|---|---|---|---|---|---|
| 1 | feature/orders-refactor | CRITICAL (14) | renameColumn on orders, composer bump, 724 lines, 26 files, no tests | DEFER | Thaw; split into expand (add grand_total) and contract (drop total) |
| 2 | chore/php-image | MEDIUM (4) | Dockerfile base image, CI pending | BLOCK | Until CI is green, then re-score |
| 3 | fix/checkout-tax-rounding | MEDIUM (3) | checkout path, tests added | SHIP-WITH-GUARDS | Tue 17 Nov 11:00, author present, 60-min watch on checkout errors |
| 4 | fix/banner-copy | LOW (0) | translations and docs only | SHIP | Mon 16 Nov |
| 5 | feature/recs-widget | LOW (0) | flag default off, tests added | SHIP | Mon 16 Nov; flag stays off until 2 Dec |
Thaw order: 1) Wed 2 Dec chore/php-image (once green) 2) Thu 3 Dec orders expand migration + dual-write code 3) Tue 8 Dec contract migration dropping total.
Open question: who approves hard-freeze exceptions (must not be the author)?
Connects securely to your tools. The creator never sees your data.
About this skill
A code freeze is only as good as the decisions made in the days before it. This skill turns a pile of open pull requests, unmerged branches and "just one small fix" requests into a ranked, defensible list: what ships before the freeze, what ships only behind guards, what waits until the thaw, and what is blocked outright. Every verdict is backed by evidence from the repository (files touched, diff size, migrations, dependency and config changes, test status, rollback path), so the release owner can sign off quickly and explain each decision afterwards. It also writes the freeze calendar, the exception record for anything that must go in during the freeze, and a thaw plan so the first week after the freeze does not become an incident week.
Why it matters: Google's SRE book reports that roughly 70% of outages are due to changes in a live system (Site Reliability Engineering, O'Reilly 2016, "Tenets of SRE"; checked 13 Nov 2026). Peak traffic multiplies the cost of each of those outages.
- The team is about to enter a freeze (Black Friday 27 Nov 2026 and Cyber Monday 30 Nov 2026; year-end holidays; a product launch; a fiscal close) and has open work in flight.
- Someone asks for an exception to deploy during a freeze.
- A release owner needs a written freeze policy, calendar or go/no-go list.
- The freeze is ending and the team needs a safe thaw order.
Do not use it to review code quality in general; it judges deploy risk during a freeze window, not style.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for E-commerce.
The score is a triage aid, not a guarantee: it reads file paths, diff size and migration text, not the meaning of the code. It cannot see changes made outside git (feature-flag services, payment or CDN dashboards, DNS), so the skill asks about those and scores them by hand. Critical-path matching is by keyword in the file path and can give false positives (for example "auth" in "author"). CI status must be supplied or read from your CI; the scanner never assumes green. Default freeze dates follow the 2026 US/UK retail calendar; set your own window for other peaks.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
Git
Python 3.8+
- Optional
GitHub CLI (for PR and CI status)
Permissions
File Scopes
The bundled script only runs git diff and git rev-parse. It never checks out, merges, pushes or deploys anything.