converge

Audits and fixes repository drift against dev-env skill contracts.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/brandonarbini/arbini.family --skill converge-brandonarbini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: converge
Source: https://github.com/brandonarbini/arbini.family/tree/main/.agents/skills/converge
Command: npx skills add https://github.com/brandonarbini/arbini.family --skill converge-brandonarbini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories drift out of compliance with shared dev-env standards over time, causing CI failures and inconsistent agent configuration files like AGENTS.md, CLAUDE.md, and .cursor/rules. This Skill turns "bring this repo up to standard" into a concrete, repeatable audit-and-fix procedure instead of ad hoc guesswork. ## Core Features & Use Cases - Contract Auditing: Reads every .agents/skills/*/SKILL.md with a ## Contract section and checks each bullet as a statement that must be true of the repo right now. - Guided Remediation: Fixes deviations using the guidance in each skill's own body, while protecting dev-env-generated files from hand edits that would be silently reverted. - Verified PR Workflow: Verifies fixes inside the devcontainer with lint, typecheck, and test commands, then opens a PR titled "Converge on dev-env standards" with one commit per unrelated item. - Use Case: When CI starts failing right after shared dev-env standards change, run this Skill to audit every contract bullet, fix drift in AGENTS.md or CLAUDE.md, verify in the devcontainer, and open a reviewable PR. ## Quick Start Converge this repo on the current dev-env standards and open a PR with the fixes.

Frequently Asked Questions about converge

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

FAQPage Schema
How do I bring a repo up to dev-env standards?▼

Run the converge procedure: read every .agents/skills/*/SKILL.md contract section, audit the repo against each bullet, fix deviations using the guidance in each skill's body, verify inside the devcontainer, and open a PR titled "Converge on dev-env standards".

What must AGENTS.md contain in a dev-env repo?▼

AGENTS.md holds only command routing (toolchain commands run in the devcontainer, git and gh on the host), the project's always-needed context, and a skills index table. Anything needed only sometimes belongs in a skill, not in AGENTS.md.

Can I edit files marked Generated by dev-env?▼

No. Files beginning with the line "<!-- Generated by dev-env -->" are rewritten byte-for-byte on the next dev-env apply, so hand edits are silently reverted. If the generated shape is wrong, report it upstream as a dev-env bug.

Should CLAUDE.md duplicate AGENTS.md content?▼

No. CLAUDE.md must begin with the line @AGENTS.md and contain nothing else duplicated below it. Claude Code loads AGENTS.md through that import, so a second copy of the content just goes stale.

Why should .cursor/rules .mdc files be deleted?▼

Cursor reads AGENTS.md natively, so a .mdc file is a second instruction source that inevitably drifts from it. The converge contract requires that no .cursor/rules/*.mdc files exist; delete any found rather than syncing them by hand.