skills.rest
semantic-praxis
semantic-praxisOFFICIAL
Explore all skills by this author →
GitHub

steward

Drives barwise pull requests to green by resolving CI failures, review events, and merge conflicts.

Updated Feb 17, 2026
Search Tags:#git#code review#pull request#github#issue tracker#merge conflict#ci
One-click install
npx skills add https://github.com/semantic-praxis/barwise --skill steward-semantic-praxis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: steward
Source: https://github.com/semantic-praxis/barwise/tree/main/.claude/skills/steward
Command: npx skills add https://github.com/semantic-praxis/barwise --skill steward-semantic-praxis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Driving a barwise pull request to green involves repo-specific traps that generic PR workflows cannot anticipate: git-native issue tracker conflicts, generated-file drift, stacked PRs that never receive CI, and stale remote refs that produce misleading git errors. This Skill encodes those mechanics so an agent can act on CI failures, review events, and merge conflicts correctly. ## Core Features & Use Cases - Tracker conflict resolution: Merge .beads/issues.jsonl conflicts by unioning issues by id, detecting id collisions via title comparison, and writing only through scripts/beads-crud.mjs with the strict validator gate. - Generated file and duplication handling: Regenerate drifted generated files via the regen:* scripts instead of hand-editing, and update audit-baseline.json when the duplication ratchet fires. - Pre-push verification and stacked PR recovery: Run the ordered local CI gate sequence, and push a merge of main into stacked PRs whose retarget never triggers CI. - Use Case: A PR's parent merges and GitHub retargets it to main, but no CI run starts. The Skill directs you to merge main into the branch to trigger a synchronize event, then prune stale remote refs after the branch is deleted. ## Quick Start Use the steward skill to diagnose why my barwise PR has no CI checks running and get it to green.

Frequently Asked Questions about steward

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

FAQPage Schema
How do I resolve a merge conflict in a JSONL issue tracker file?▼

Resolve .beads/issues.jsonl conflicts by taking the union of issues by id rather than picking one side. For ids changed on both sides, keep the line with the later updated_at, but first compare titles to detect id collisions, which require re-filing under a fresh id.

Why does my stacked pull request have no CI checks running?▼

The ci.yml workflow triggers only on pull_request events targeting main, so a PR based on another branch gets zero check runs. When the parent merges, the retarget fires pull_request.edited, which is outside the default activity types, so push a merge of main into the branch to trigger a synchronize event.

How do I fix a failing drift test in a generated file?▼

Fix generated-file drift by rerunning the regenerator named in the failing test's message, never by hand-editing the output. The available regenerators are the regen:* scripts in barwise/package.json, plus UPDATE_GOLDEN=1 for golden tests.

Why does git push report a new branch for a branch that already exists?▼

This symptom comes from a stale remote ref left behind when a PR merge deletes the branch. Run git remote prune origin or a bare git fetch --prune origin, because naming a branch on fetch --prune narrows the refspec and removes nothing.

What checks should I run before pushing a fix to a barwise PR?▼

Run formatting and beads strict checks first, then oxlint, depcruise, parity, and the duplication audit, followed by lint, build, and test from the barwise/ directory. Run npm run build first whenever a change crossed a package boundary, since per-package tsc reads dependencies' dist output.

Related Skills

Explore More Software Engineering Skills→
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate
michaelvolzmichaelvolz

git-clean-gone-branches

Delete local Git branches whose remote tracking branches no longer exist.

Community
Intermediate
JsplixJsplix

ibank-worklog-duplicate-audit

Audits iBank worklog datasets for duplicate entries and generates review packets.

Community
Intermediate
lightdashlightdash
6.1k

graphite

Manage stacked pull requests with Graphite CLI instead of raw git commands.

Official
Intermediate