A pull-request check system for code repositories. Pull requests are proposed changes that should pass checks before they are merged into the main codebase.

It helps design or change GitHub Actions checks for pull requests, including linting, production builds, tests with real services, dependency scans, and automatic merging.

It helps catch missing or ineffective checks, such as a build step that passes without actually compiling the project. This moves lint, build, test, dependency, and convention problems earlier in the review process.

bramka-pr — Skill for Claude Code by xentivo

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add xentivo/claude-plugins --skill bramka-pr

Clone the repo

git clone --depth 1 https://github.com/xentivo/claude-plugins

Made for: Claude Code.

Or install pipeline, the plugin that ships this one along with the rest of its 3 skills, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xentivo/claude-plugins/bramka-pr/github.svg)](https://agentmods.dev/skills/xentivo/claude-plugins/bramka-pr)

Your own site

<a href="https://agentmods.dev/skills/xentivo/claude-plugins/bramka-pr"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/bramka-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/xentivo/claude-plugins/bramka-pr"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/bramka-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,132 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00109	$0.01132
Opus 5	$0.00055	$0.00566
Sonnet 5	$0.00022	$0.00226
Haiku 4.5	$0.00011	$0.00113

Measured 9d ago against content hash a85596258a77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bramka-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pipeline/skills/bramka-pr/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bramka na pull requestach

Zielona bramka jest warta tyle, ile łapie. Dwa najdroższe błędy to check, którego nie ma (błąd wychodzi po merge'u), i check, który przechodzi, bo nic nie sprawdził.

Pełna zasada organizacji: get_rule("ci-pipeline") na serwerze Xentivo MCP. Poniżej procedura; uzasadnienia i historie wpadek są w zasadzie.

Zanim dopiszesz jakikolwiek job

Sprawdź, co realnie łamie się w tym repo po merge'u. Bramka powstaje z incydentu, nie z listy dobrych praktyk.
Przeczytaj Dockerfile albo skrypt buildu. Job budujący ma odtwarzać ten build, który poleci do rejestru, z tymi samymi zmiennymi-placeholderami.
Sprawdź, co jest w .gitignore, a co importuje kod (klient ORM, kod generowany). Każdy job kompilujący musi mieć swój krok generujący.

Zestaw minimalny

Lint - osobno od testów, bo nie potrzebuje bazy i daje wynik po minucie.
Build produkcyjny - osobna bramka. Bez niej błąd typów wychodzi dopiero przy budowaniu obrazu w deployu, czyli po merge'u do pnia.
Testy - z prawdziwymi usługami w services:, na obrazach identycznych z tymi, których używa deweloper lokalnie.
Skan zależności - z zależnościami deweloperskimi, z kontrolą „ile paczek faktycznie przeskanowano" i z progiem blokującym zapisanym czytelnie w kroku.
Bramka konwencji (baza PR-a, nazwa gałęzi) - sekundowy job bez if na poziomie joba, żeby przy naruszeniu zapalił się na czerwono, a nie pominął. Trzymaj ją w osobnym pliku od lintu, buildu i testów (patrz reguła niżej).

Reguły, których nie negocjujemy

Wyzwalacz dla checków czytających KOD: [opened, synchronize, reopened, ready_for_review]. Bez ostatniego PR wyjęty z drafta nie dostaje żadnego zdarzenia.
Bramka na metadane PR-a idzie do osobnego pliku i słucha dodatkowo edited, labeled i unlabeled. Bazę PR-a przestawia się z UI, a to edited, nie synchronize, więc bez tych zdarzeń check zostaje z wynikiem sprzed zmiany. Nie dokładaj tych zdarzeń do pliku z lintem i testami „z warunkiem na rodzaj zdarzenia": job pominięty przez if raportuje skipped, a wymagany check w tym stanie liczy się przy ochronie gałęzi jak zielony - czyli jedna etykieta nadpisuje czerwone testy zielonym pominięciem.
concurrency po numerze PR-a z cancel-in-progress: true.
permissions: contents: read na górze pliku; szerzej tylko w jobie, który tego potrzebuje.
Job doradczy (recenzja AI, komentarz bota) ma continue-on-error: true i nigdy nie jest wymaganym checkiem.
Warunek zależny od sekretu piszesz na env, nie na secrets - kontekst secrets w if nie działa i cicho daje fałsz.

Read the full file on GitHub · 63 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 63 lines · 109 tokens per session scan A a85596258a77

Subscribe to this mod's changes

bramka-pr is a skill published in the GitHub repository xentivo/claude-plugins (3 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 1,132 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CI and CD DevOps and cloud Git and workflow

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

atmos-hooks

Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.

cloudposse/atmos · 46 tokens

atmos-pro

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.

cloudposse/atmos · 38 tokens

start-temps-cluster

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…

gotempsh/temps · 204 tokens

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon/Citadel · 46 tokens