tda-agent-safety-guardrails

Enforce and review code operation boundaries, git rules, and file write restrictions.

1|Updated Dec 13, 2025

Search Tags:#developer tools #code review #git operations #security compliance #safety guardrails

Ready to run

npx skills add https://github.com/stephendor/TDL --skill tda-agent-safety-guardrails

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tda-agent-safety-guardrails
Source: https://github.com/stephendor/TDL/tree/main/.agents/skills/tda-agent-safety-guardrails
Command: npx skills add https://github.com/stephendor/TDL --skill tda-agent-safety-guardrails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures adherence to safety boundaries when configuring or reviewing agent safety in TDL, safeguarding against destructive commands and unauthorized actions.

Core Features & Use Cases

Boundary Configuration: Define and review safety boundaries like git operation rules, file-write restrictions, and result-protection policies.
Guardrail Enforcement: Verify active pre-commit and write-time hooks for secure development practices.
Task Review Support: Facilitates the review of code, methods, and work products for safety compliance.
Use Case: For a new code review, activate the Skill to automatically check for compliance with established safety guardrails.

Quick Start

Run 'tda-agent-safety-guardrails' to perform a safety check on the current codebase.

Frequently Asked Questions about tda-agent-safety-guardrails

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

FAQPage Schema

How do I enforce safety guardrails for automated git operations?▼

Safety guardrails for git operations are enforced by defining operation rules and verifying active pre-commit hooks to prevent destructive commands. This secures automated development workflows against unauthorized actions.

What are agent safety boundaries in software development workflows?▼

Agent safety boundaries are configured limits that restrict file writes, enforce git rules, and establish result-protection policies. They safeguard the codebase by preventing autonomous agents from executing destructive or unauthorized actions.

How do I check my codebase for security compliance before a code review?▼

Security compliance is checked by running a safety guardrails review on the current codebase. This verifies active write-time hooks and validates that established file write restrictions and git operation rules are properly applied.

Do I need to configure Git hooks manually to enforce file write restrictions?▼

Configuring Git hooks manually is not required for file write restrictions when using automated safety guardrails. The system verifies active pre-commit and write-time hooks to enforce secure development practices automatically.

What is the best way to prevent destructive git commands in automated agent workflows?▼

The best way to prevent destructive git commands is to enforce predefined agent safety boundaries. This reviews code methods and work products, applying result-protection policies and strict operation rules to block unauthorized actions.

When should I not use automated safety guardrails for code review?▼

Automated safety guardrails may not suit code reviews lacking established git rules or file write restrictions. If your development workflow has no pre-commit hooks or defined safety boundaries, the enforcement review cannot operate effectively.