A contributor procedure for taking an already opened pull request through checks, review feedback, conflict resolution, and merging. A pull request is a proposed code change submitted for review before it is added to the main project.

Use it to run the local CI check, investigate failed pipeline jobs, resolve recurring conflicts, handle AI review comments, and merge a green pull request.

It gives a repeatable response to failed checks, merge conflicts, and automated review comments. It also defines when a change is ready to merge and when the user must see it first.

steward — Skill for Claude Code by mendixlabs/mxcli

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 mendixlabs/mxcli --skill steward

Clone the repo

git clone --depth 1 https://github.com/mendixlabs/mxcli

Made for: Claude Code.

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/mendixlabs/mxcli/steward/github.svg)](https://agentmods.dev/skills/mendixlabs/mxcli/steward)

Your own site

<a href="https://agentmods.dev/skills/mendixlabs/mxcli/steward"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/steward/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/mendixlabs/mxcli/steward"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/steward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,669 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.00089	$0.01669
Opus 5.5	$0.00036	$0.00668
Sonnet 5.5	$0.00018	$0.00334
Haiku 4.5	$0.00009	$0.00167

Measured today against content hash 731ecc30fcfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

steward 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 today.

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.

.claude/skills/steward/SKILL.md · 122 lines

How it starts

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

Find it fast

sed -n '<from>,<to>p' SKILL.md one section rather than reading the file; ./mxcli syntax <topic> answers how do I write this for a fraction of either.

lines	section
27-54	Merge on green is the default
55-72	Before every push: `make ci-local`
73-87	Reading a red CI job
88-103	Conflicts this repo keeps hitting
104-121	The AI PR Review comment

Steward: Driving a PR to Merged

This is a contributor skill (dev-only); it is not synced to user projects. It holds this repository's conventions for the loop after a PR is opened. How to make the change itself is /mxcli-dev:fix-issue and the CLAUDE.md working rules; this file starts where they stop.

Merge on green is the default

The user reviews a change in the session, before the PR exists. So:

Open a PR only after the user has seen the change summarized in the session and asked for it. Never open one to get a review.
Once it is open, merge it without asking again as soon as all of these hold on the current head:
- every job of Build, Test & Lint (.github/workflows/push-test.yml) is green, integration-passed included. A push to the PR branch runs that workflow twice on the same commit, for the push and the pull_request event; a job that passed in one run and was cancelled before it got a runner in the other counts as green;
- GitHub reports no merge conflict;
- no human review thread or changes-requested review is open;
- no Critical item from the AI PR Review comment is unanswered (see below).
Merge with a merge commit (not squash, not rebase), passing the head SHA you checked as expectedHeadSha, so a push that lands in between is not merged unseen.
After the merge, unsubscribe from the PR, cancel its pending check-in, and restart the working branch from the new main: git fetch origin main && git checkout -B <branch> origin/main, then push. The next PR starts from there; never stack new work on merged history.

Read the full file on GitHub · 122 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.

today First seen · 122 lines · 89 tokens per session scan A 731ecc30fcfb

Subscribe to this mod's changes

steward is a skill published in the GitHub repository mendixlabs/mxcli (132 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 1,669 once invoked, about $0.0004 per session on Opus 5.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-10-30.

Code review Git and workflow Releases agentic claude cli genai mdl mendix

autofix-pr

Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…

QwenLM/qwen-code · 123 tokens

triage

Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.

QwenLM/qwen-code · 50 tokens

github

Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.

Hmbown/Codewhale · 0 tokens

bump-version

A release procedure for termio, a macOS app, that creates a numbered Git tag on the main branch. A Git tag is a permanent label for a specific version of the code.

termio-sh/termio · 66 tokens

release

Cut a new gflow-cli release — bump version, update CHANGELOG, tag, push, and back-merge.

ffroliva/gflow-cli · 26 tokens

testflight-release

Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…

termio-sh/termio · 102 tokens