rb-safe-operation

Execute static-only, schema-3 constrained plans with coordinator-led patch validation.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-safe-operation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-safe-operation
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-safe-operation
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-safe-operation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pydantic, pydantic-ai-slim, openai, tiktoken, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill provides a secure, deterministic workflow for applying code changes that require static verification, preventing unauthorized execution or runtime side effects.

Core Features & Use Cases

  • Static Verification: Ensures all success criteria are observable through static file state, eliminating risks from hidden runtime behaviors.
  • Bounded Proposal Workflow: Uses a coordinator-led process to assess and apply patches, ensuring every change is validated against project policy.
  • Use Case: Use this skill when you need to apply a critical configuration update or schema change to a production repository where executable tests or external network calls are strictly prohibited.

Quick Start

Use the rb-safe-operation skill to check readiness and prepare the execution authority for the current project plan.

Frequently Asked Questions about rb-safe-operation

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

FAQPage Schema
How do I apply static analysis patches without triggering runtime side effects?

Static analysis patches are applied through a deterministic coordinator that validates all file-state mutations, ensuring changes are observable statically without triggering runtime side effects. This bounded workflow enforces preflight checks before applying any patch.

What is the best way to enforce compliance and governance for production repository updates?

Compliance and governance for production updates are enforced using schema-3 constrained plans validated against project policy. The coordinator-led process maintains an immutable audit trail, satisfying strict governance requirements for high-integrity environments.

How do I execute configuration updates when external network calls are strictly prohibited?

Configuration updates are executed through static-only, non-executable operations that enforce preflight checks. This prevents unauthorized execution and external network calls by ensuring all success criteria are observable through static file state.

Can I use automated patch management in environments requiring immutable audit trails?

Automated patch management is supported in environments requiring immutable audit trails through coordinator-led patch application. It separates static verification and validates every file-state mutation against project policy before applying changes.

What are the limitations of static verification for code changes?

Static verification is limited to changes where success criteria are observable through static file state. It does not support operations relying on hidden runtime behaviors, executable tests, or external network calls.

Does static verification require any specific environment setup before applying schema changes?

Static verification requires checking readiness and preparing the execution authority for the current project plan. This ensures the environment is properly configured for the deterministic coordinator to validate file-state mutations safely.