freeze

Lock a codebase by writing a .freeze file with reason, timestamp, and branch.

70|42|Updated Mar 27, 2026

Search Tags:#deployment #release-management #hotfix #git-branch #stabilization #code-freeze

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill freeze-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/freeze
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill freeze-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents non-critical merges during release cutovers by creating a simple lock marker so the branch state remains stable and predictable.

Core Features & Use Cases

Freeze tracking: Reads an existing .freeze file and confirms whether overriding the current lock is desired.
Structured lock creation: Captures the freeze reason, ISO timestamp, and branch name when git is available before writing the file.
Release discipline: Ideal for locking main before deployment, enforcing hotfix-only work, and guiding the team toward the next checklist actions.

Quick Start

Use /freeze with the final release reason to lock the main branch before the cut and notify the team.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I lock a git branch to prevent non-critical merges during a release?▼

To lock a git branch during a release, you can apply a code freeze by writing a .freeze file. This lock marker captures the freeze reason, timestamp, and branch name to keep the branch state stable and predictable.

What is a code freeze and when should I use it for deployment stabilization?▼

A code freeze is a locking mechanism that prevents non-critical merges during high-stakes deployments. You should use it during release cutovers, hotfix deployments, and stabilization periods to maintain branch stability.

Can I override an existing branch freeze lock if a new deployment is needed?▼

Yes, you can override an existing branch freeze lock. When a .freeze file already exists, the system reads the current lock metadata and prompts you to confirm whether overriding the active lock is desired before proceeding.

What metadata is required to enforce a release branch code freeze?▼

Enforcing a release branch code freeze requires capturing the freeze reason, ISO timestamp, and branch name. When git is available, this metadata is structured and written into a .freeze file to record the lock context.

Does a code freeze block all git merges or only non-critical hotfix deployments?▼

A code freeze specifically blocks non-critical merges to enforce release discipline. It is designed to lock the main branch before deployment, guiding the team to focus on hotfix-only work and follow the next checklist actions.