Run any Skill in Manus with one click

Get Started

backpressure

Stars2

Forks1

UpdatedMarch 18, 2026 at 21:15

How to run and interpret backpressure checks. Use before committing code to ensure quality gates pass.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dgbau

dgbau/rl

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	backpressure
description	How to run and interpret backpressure checks. Use before committing code to ensure quality gates pass.

Backpressure

Backpressure is the mandatory quality gate that runs before every commit. Nothing gets committed without passing.

Command

The backpressure command is project-specific. Read it from .ralphrc:

# Source the config to get BACKPRESSURE_CMD
source .ralphrc
eval "$BACKPRESSURE_CMD"

Common examples of BACKPRESSURE_CMD:

npx nx affected -t lint test build -- Nx monorepo
npm run lint && npm test && npm run build -- standard npm project
make lint test build -- Makefile-based project
cargo clippy && cargo test && cargo build -- Rust project

If BACKPRESSURE_CMD is not set, check AGENTS.md for the project's quality gate commands.

Interpreting Failures

Lint failures

Linter errors in changed files (ESLint, clippy, pylint, etc.)
Fix: read the error, apply the fix, re-run
Common: unused imports, missing types, formatting issues

Test failures

Unit test assertions failing
Fix: check if test expectation is correct or if implementation has a bug
If the test is wrong: fix the test
If the implementation is wrong: fix the implementation

Build failures

Compilation errors or build tool failures
Fix: read the error, fix the type mismatch or missing dependency
Common: missing exports, incorrect import paths, type mismatches

Self-Heal Protocol

If backpressure fails after an iteration:

Read the error output carefully
Fix all failures
Re-run the backpressure command (from BACKPRESSURE_CMD in .ralphrc)
Only commit when all checks pass
If still failing after one fix attempt, stop and report the issue

Rules

NEVER skip backpressure
NEVER commit code that fails quality gates
Run backpressure on affected code only (not the entire project) when the tooling supports it
If a pre-existing failure exists in an unrelated area, note it but don't block on it
The backpressure command may vary between projects -- always read it from .ralphrc

More from this repository

same repository

openspec-sync-specs

dgbau/rl

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

2026-04-032

github-pr-review

dgbau/rl

Fetching and addressing GitHub PR review comments from Copilot, Greptile, and human reviewers. Includes provider-calibrated triage, verification, ticket management, and conditional spec updates. Use when in review mode or when PR feedback needs to be addressed.

Core Ralph Loop workflow orchestration. Use when running autonomous development iterations, selecting modes, or making decisions about the build/interview/bootstrap/archive lifecycle.

2026-03-232

ralph-workflow

dgbau/rl

Core Ralph Loop workflow orchestration. Use when running autonomous development iterations, selecting modes, or making decisions about the build/interview/bootstrap/archive lifecycle.

2026-03-182

openspec-apply-change

dgbau/rl

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

2026-03-182

name	backpressure
description	How to run and interpret backpressure checks. Use before committing code to ensure quality gates pass.

Backpressure

Backpressure is the mandatory quality gate that runs before every commit. Nothing gets committed without passing.

Command

The backpressure command is project-specific. Read it from .ralphrc:

# Source the config to get BACKPRESSURE_CMD
source .ralphrc
eval "$BACKPRESSURE_CMD"

Common examples of BACKPRESSURE_CMD:

npx nx affected -t lint test build -- Nx monorepo
npm run lint && npm test && npm run build -- standard npm project
make lint test build -- Makefile-based project
cargo clippy && cargo test && cargo build -- Rust project

If BACKPRESSURE_CMD is not set, check AGENTS.md for the project's quality gate commands.

Interpreting Failures

Lint failures

Linter errors in changed files (ESLint, clippy, pylint, etc.)
Fix: read the error, apply the fix, re-run
Common: unused imports, missing types, formatting issues

Test failures

Unit test assertions failing
Fix: check if test expectation is correct or if implementation has a bug
If the test is wrong: fix the test
If the implementation is wrong: fix the implementation

Build failures

Compilation errors or build tool failures
Fix: read the error, fix the type mismatch or missing dependency
Common: missing exports, incorrect import paths, type mismatches

Self-Heal Protocol

If backpressure fails after an iteration:

Read the error output carefully
Fix all failures
Re-run the backpressure command (from BACKPRESSURE_CMD in .ralphrc)
Only commit when all checks pass
If still failing after one fix attempt, stop and report the issue

Rules

NEVER skip backpressure
NEVER commit code that fails quality gates
Run backpressure on affected code only (not the entire project) when the tooling supports it
If a pre-existing failure exists in an unrelated area, note it but don't block on it
The backpressure command may vary between projects -- always read it from .ralphrc