القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turns real agent failures, repeated prompts, team-specific workflows, and durable project lessons into better SDD skills or memory entries. Use when the user asks to create/update/refine skills, extract reusable lessons, improve skill routing, encode team process, or save patterns for future sessions.
Provides the vendored agent-style v0.3.5 prose rule pack as a portable Claude skill. Use when installing, syncing, applying, or auditing SDD Agent-Style support in another project, or when a style-review workflow needs the bundled rules.
Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.
Scans Markdown (.md) files for malicious code injection including XSS, prompt injection, script injection, obfuscated payloads, and supply chain attack vectors. Use when auditing .md files for security threats or when the user mentions scanning markdown for malicious content.
Provides .NET and ASP.NET Core patterns for REST APIs, Entity Framework, dependency injection, and middleware. Use when working with C# files (*.cs, *.csproj) or when the user mentions .NET, ASP.NET Core, C#, or Entity Framework.
Designs hybrid cloud architectures connecting on-premises infrastructure with public cloud services. Use when designing systems spanning on-prem and cloud, or when the user mentions hybrid cloud or multi-environment architecture.
| name | freeze |
| description | 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. |
| argument-hint | [reason] |
| user-invocable | true |
| allowed-tools | Read, Write, Bash |
| effort | 1 |
| agent | release-manager |
| when_to_use | Before release cut, hotfix deployment, or when a stabilization period is needed |
Lock the codebase in preparation for a release. Create a .freeze file containing freeze information.
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.
If no argument is provided, ask:
"What is the reason for the freeze? (e.g., 'Release v2.1.0', 'Hotfix deployment', 'Sprint end')"
.freeze FileWrite the following content:
FROZEN=true
REASON=[reason]
FROZEN_AT=[ISO timestamp]
BRANCH=[current branch from git rev-parse --abbrev-ref HEAD]
Display:
🔒 CODEBASE FROZEN
Reason : [reason]
Time : [timestamp]
Branch : [branch]
Non-critical merges are blocked. Only hotfixes are permitted.
To unlock: /unfreeze
/release-checklist — Run the full release checklist/guard — Check the freeze status at any time/unfreeze — Unlock after the release is complete.freeze but omit the BRANCH field./guard — Check freeze status before merge/deploy/unfreeze — Remove freeze after release/release-checklist — Full release workflow/hotfix — Deploy urgent fixes during a freeze