Freeze
Skill tranhieutt/software_development_department/.claude/skills/freeze
Locks the codebase to prevent unintended writes during a freeze period such as before a release or during an incident. Use when the user mentions freezing, code lock, or release lockdown.From its SKILL.md
npx -y skills add tranhieutt/software_development_department --skill freezeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.9 KB, 387 tokens by cl100k_base, as published. Nobody here has run it
Code Freeze
Lock the codebase in preparation for a release. Create a .freeze file containing freeze information.
Workflow
1. Read Current Status
Check if .freeze already exists by reading the file. If it exists, display the information and ask:
"The codebase is currently frozen for: [REASON]. Do you want to override the current freeze? (yes/no)"
If no, stop.
2. Get Freeze Reason
If no argument is provided, ask:
"What is the reason for the freeze? (e.g., 'Release v2.1.0', 'Hotfix deployment', 'Sprint end')"
3. Create .freeze File
Write the following content:
FROZEN=true
REASON=[reason]
FROZEN_AT=[ISO timestamp]
BRANCH=[current branch from git rev-parse --abbrev-ref HEAD]
4. Notification
Display:
π CODEBASE FROZEN
Reason : [reason]
Time : [timestamp]
Branch : [branch]
Non-critical merges are blocked. Only hotfixes are permitted.
To unlock: /unfreeze
5. Suggested Next Steps
/release-checklistβ Run the full release checklist/guardβ Check the freeze status at any time/unfreezeβ Unlock after the release is complete
Edge Cases
- Existing freeze: Ask for override confirmation before overwriting.
- No git repository: Still create
.freezebut omit the BRANCH field.
Related Skills
/guardβ Check freeze status before merge/deploy/unfreezeβ Remove freeze after release/release-checklistβ Full release workflow/hotfixβ Deploy urgent fixes during a freeze
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.