skills.rest
netbrain
netbrainCOMMUNITY
Explore all skills by this author →
Website𝕏@netweedGitHub

ratchet:tighten

Analyze Ratchet improvement signals and generate prioritized fixes for prompts, guards, and workflows.

1|Updated Mar 12, 2026
Search Tags:#workflow#triage#ci#guards#pr-review#ratchet#tighten
One-click install
npx skills add https://github.com/netbrain/ratchet --skill ratchet-tighten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ratchet:tighten
Source: https://github.com/netbrain/ratchet/tree/main/skills/tighten
Command: npx skills add https://github.com/netbrain/ratchet --skill ratchet-tighten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tighten the ratchet centralizes and prioritizes improvement signals across a Ratchet workspace so maintainers can convert debate history, CI failures, PR feedback, retros, and escalations into concrete, safe fixes that reduce recurring issues and improve agent prompts, guards, and workflow configuration.

Core Features & Use Cases

  • Signal aggregation: Collects debates, retros, escalations, executions, discoveries, and PR-specific CI and review data from the .ratchet directory and GitHub.
  • Analyst + verifier pipeline: Produces a prioritized plan with an analyst (generative) that proposes fixes and an adversarial verifier that fact-checks findings before any edits.
  • Automated changes with human guardrails: Prepares prompt edits, guard additions, workflow.yaml changes, retros, and optional caveman token-compression, always asking for user confirmation before writing or committing.
  • Persistence and reporting: Writes retros/reports, creates discoverable sidequests for skipped findings, stages .ratchet changes and offers commit/PR workflows.
  • Use case examples: Triaging a failing PR to decide if the failure is caused by the PR, sharpening adversarial validation commands, and compressing verbose pair prompts to save tokens.

Quick Start

Use /ratchet:tighten to analyze project signals, prioritize gaps, and propose verified fixes for prompts, guards, and workflow settings.

Frequently Asked Questions about ratchet:tighten

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

FAQPage Schema
How do I triage CI failures and PR review feedback in a Ratchet workspace?▼

You can triage CI failures and PR review feedback by analyzing .ratchet artifacts and GitHub data to prioritize fixes for pair prompts, guards, and workflow configuration.

How do I convert retros and debate history into concrete workflow.yaml fixes?▼

Converting retros and debates into workflow.yaml fixes involves an analyst pipeline that proposes changes and an adversarial verifier that fact-checks findings before preparing git commits.

What is the best way to compress verbose pair prompts to save tokens?▼

Compressing verbose pair prompts to save tokens is handled through optional caveman token-compression, which proposes prompt edits and asks for user confirmation before writing changes.

Does the ratchet tighten workflow automatically commit changes to the repository?▼

The ratchet tighten workflow does not automatically commit changes; it stages .ratchet artifacts, prepares git commits or PR branches, and always asks for user confirmation before writing.

Can I use this to decide if a failing PR is caused by the PR itself or existing guards?▼

You can use this to decide if a failing PR is caused by the PR itself by triaging PR-specific CI and review data against repository state to isolate the root cause.

What happens to skipped findings during Ratchet signal triage?▼

Skipped findings during Ratchet signal triage are preserved by creating discoverable sidequests, ensuring no improvement signal is lost while focusing on prioritized fixes.

Related Skills

Explore More Software Engineering Skills→
netbrainnetbrain
1

ratchet:watch

Monitor Ratchet PRs for merge conflicts, CI failures, and review comments.

Community
Advanced
sqfzysqfzy

git

Generate conventional commit messages and update changelogs from repository state.

Community
Advanced
andrewthetechieandrewthetechie
2

prd-review

Fact-check PRD claims against repository code and architecture.

Community
Advanced
drndrn
23

debug

Orchestrate AI investigators to test hypotheses and identify root causes.

Community
Advanced