AgentStack
SKILL verified MIT Self-run

Guard

skill-tranhieutt-software-development-department-guard · by tranhieutt

Enforces project safety constraints by blocking risky operations outside their approved scope during active development. Use when activating a safety guard or constraint for the current session.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-tranhieutt-software-development-department-guard

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Guard? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Guard Check

Check the freeze status of the codebase. Use as a gate check before any operations on the main branch.

Workflow

1. Read .freeze

If it does not exist:

✅ CLEAR — No active freeze.
Development and merging can proceed normally.

Stop here.

If it exists, proceed to step 2.

2. Display Freeze Warning

🔒 CODEBASE IS FROZEN

Reason  : [REASON from .freeze]
Since   : [FROZEN_AT]
Branch  : [BRANCH]
Duration: [calculated from FROZEN_AT to current time]

⚠️  Non-critical merges are blocked during a freeze period.

3. Categorize the Request

Ask: > "What type of operation is this?" > > A) Urgent Hotfix — production bug, security patch > B) Release Artifact — changelog, version bump, release notes > C) Non-critical — feature, refactor, chore, normal docs

If A or B: Allow to proceed with a note: > "⚠️ Permitted to proceed. Note that this is a freeze period — execute only necessary operations."

If C: Block and instruct: > "🚫 Non-critical changes must wait until after /unfreeze. > Save your work and continue after the release is complete."

4. Suggestions

  • /unfreeze — If the release is finished
  • /release-checklist — If currently in the release process
  • /hotfix — If an urgent fix deployment is needed

Edge Cases

  • No .freeze: Just report CLEAR, ask no further questions.
  • User unsure of operation type: Ask for more details to categorize correctly before deciding.

Related Skills

  • /freeze — Lock codebase
  • /unfreeze — Remove freeze
  • /hotfix — Urgent deployment during freeze
  • /release-checklist — Full release workflow

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.