sentinel-ops

Coordinate multi-repo CI/CD governance for Consistency Sentinel across huanlongAI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/huanlongAI/tzh-Harness --skill sentinel-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentinel-ops
Source: https://github.com/huanlongAI/tzh-Harness/tree/main/cowork-skills/sentinel-ops
Command: npx skills add https://github.com/huanlongAI/tzh-Harness --skill sentinel-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-repo CI/CD governance for Consistency Sentinel across the huanlongAI organization requires repeatable patterns, clear ownership, and robust error handling. This skill consolidates the operational knowledge to deploy, debug, configure, and manage the Sentinel framework across all repos with minimal manual friction.

Core Features & Use Cases

  • Hub-and-spoke reusable workflow pattern for cross-repo governance
  • Per-repo configuration, prechecks, LLM-driven review, and batch deployment
  • Dashboards and monitoring to track health, escalations, and compliance across the org

Quick Start

Configure and run cross-repo Sentinel workflows by applying the hub-and-spoke pattern, enabling prechecks, LLM review, and cross-repo dispatch across the huanlongAI org.

Frequently Asked Questions about sentinel-ops

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

FAQPage Schema
How do I coordinate multi-repo CI/CD governance across an organization?

Multi-repo CI/CD governance can be coordinated using a hub-and-spoke reusable workflow pattern to apply per-repo policies, prechecks, and batch deployments across all guarded repositories.

How do I configure per-repo policies for CI/CD workflows?

Per-repo policies are configured through a centralized hub-and-spoke pattern, enabling individual repositories to enforce specific prechecks, LLM reviews, and deployment rules while maintaining organizational consistency.

What is the best way to add LLM review to a CI/CD pipeline?

Adding LLM review to a CI/CD pipeline is best achieved by integrating an LLM review step within your reusable workflow, utilizing an ANTHROPIC_API_KEY to evaluate code changes before batch deployment.

Do I need cross-repo tokens to manage multi-repo CI/CD operations?

Yes, cross-repo secret management requires a CASCADE_TOKEN and ANTHROPIC_API_KEY to securely dispatch workflows, handle permissions, and perform LLM reviews across multiple guarded repositories.

How do I monitor CI/CD compliance and health across multiple repositories?

Monitoring CI/CD compliance across multiple repositories is done by deploying dashboards that track health, escalations, and policy adherence, ensuring disaster-safe operations across the entire organization.

Can I use public, ASCII-only YAML for multi-repo CI/CD workflows?

Yes, multi-repo CI/CD workflows support public, ASCII-only workflow YAMLs, ensuring clear permissions handling and structured outputs while maintaining strict governance across all repositories.