New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cross Repo Change

by awebai in awebai/aweb

Coordinate changes that touch both the aweb OSS repo and the hosted ac repo.

MITAuto-check passed

Install Cross Repo Change

skills CLI
$ npx skills add awebai/aweb --skill cross-repo-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install awebai/aweb cross-repo-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/awebai/aweb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cross-repo-change .claude/skills/cross-repo-change && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cross-repo-change
GitHub stars
115
Token cost
~1.5k tokens
SKILL.md length
893 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Coordinate changes that touch both the aweb OSS repo and the hosted ac repo.

  • Works in 6 steps: Design — agree on the contract change… → OSS first — land the OSS change on aweb… → Release OSS — run make release-candidate… → …
  • SKILL.md covers Read this first: shippability, Principle (aweb ↔ ac only), Sequence and Anti-patterns, plus 3 more sections
  • Calls make and npm

What it does

Cross Repo Change is an agent skill from awebai/aweb. Coordinate changes that touch both the aweb OSS repo and the hosted ac repo. OSS lands first; the hosted repository owns dependency derivation and deployment.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Communication for AI agents: stable identity, durable mail and chat, and wake-up events across sessions, runtimes, machines, and organizations. MIT, self-hostable. The licence is MIT.

Example prompts

  • “/cross-repo-change”

Requirements

  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Design — agree on the contract change between OSS and cloud.
  2. OSS first — land the OSS change on aweb main after the relevant focused
  3. Release OSS — run make release-candidate TAGS='...' in aweb, then push
  4. Cloud pins — update and review backend/pyproject.toml and
  5. Cloud candidate — land the cloud-side source change on AC main, then
  6. Verify — cloud tests pass against the real aweb package (not

What it can do on your machine

Read from SKILL.md and the folder at commit 3fbb43c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross Repo Change loads about 1.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 893 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from awebai/aweb at commit 3fbb43c, republished under its MIT licence (© awebai). 893 words, ~1,510 tokens.

Download SKILL.mdSave it as .claude/skills/cross-repo-change/SKILL.md (or your agent's skills folder).
name
cross-repo-change
description
Coordinate changes that touch both the aweb OSS repo and the hosted ac repo. OSS lands first; the hosted repository owns dependency derivation and deployment.

Cross-repo change coordination

Changes that affect both aweb (OSS) and ac (hosted SaaS) must be coordinated carefully because ac embeds aweb as a PyPI package.

Read this first: shippability

A released client is a permanent constraint. Once a client that sends X is in the field, the server must accept X until you can prove nothing sends it.

Everything below about atomic deploys applies to aweb ↔ ac only. Every other consumer — the channel plugin, pi, the aw CLI, self-hosted servers — updates on its own schedule. A running agent keeps its loaded module until the process restarts, which for a long-lived agent may be never.

Default: additive only. You may ADD an accepted shape. You may NOT:

  • remove an accepted shape,
  • make an optional field required,
  • reject a shape that is in the field,
  • narrow a type or add a stricter validator to an existing field.

The only exception: you may narrow a contract if you can NAME every consumer and show each deploys atomically with this change — same image, same deploy, same instant. "We will release the client right after" is not atomic. Put the justification in the commit message. Today exactly one boundary qualifies: aweb ↔ ac.

Removal is a separate, later change. Remove support for an old shape only after MEASURING that nothing sends it. If you cannot measure it, you cannot remove it.

Before merge, answer: what is deployed today, and does this still work against it? Check against PUBLISHED ARTIFACTS — npm pack the tarball and read the shipped bundle, or read the released tag — never against your own source. Your source and the published client disagree; that disagreement is the entire risk.

Why this section exists: on 2026-07-26 a chat mark-read change made a new field required and explicitly rejected the old one. Every published client sent the old field, so deploying it would have broken every client in the world. It was faithful to the anti-pattern below, which is correct for the cloud boundary and catastrophic for clients. The process was not ignored — it was followed.

Principle (aweb ↔ ac only)

The cloud imports aweb. Both deploy in the same Docker image. There is no transition period — when the cloud pins a new aweb version, both the old and new code deploy atomically.

This is the ONLY boundary with that property. Do not generalise it.

Sequence

  1. Design — agree on the contract change between OSS and cloud. Identify which side goes first.

  2. OSS first — land the OSS change on aweb main after the relevant focused tests pass.

  3. Release OSS — run make release-candidate TAGS='...' in aweb, then push each resulting tag separately. docs/release.md is authoritative. Wait for the exact package versions to be public.

  4. Cloud pins — update and review backend/pyproject.toml and backend/uv.lock to the exact public OSS versions on AC main.

  5. Cloud candidate — land the cloud-side source change on AC main, then run make release-candidate VERSION=X.Y.Z. Push the resulting vX.Y.Z tag; AC never publishes OSS artifacts.

  6. Verify — cloud tests pass against the real aweb package (not editable/sibling source).

Show full SKILL.md (388 more words)Show less

Anti-patterns

  • Do NOT land the cloud change before the OSS release. The cloud CI will fail on import errors.
  • Do NOT use editable/sibling source installs as a permanent workaround. They mask version pinning issues.
  • Do NOT accept both old and new formats "during transition" when both sides deploy atomically. Pick one format. This applies to aweb ↔ ac and nowhere else. Before invoking it, confirm every consumer of the contract deploys in that same image. If any consumer is a published client — channel, pi, aw — or a self-hosted server, the rule INVERTS: accept both, prefer the new one, and remove the old only after measuring. See "Read this first: shippability".
  • Do NOT change a contract without enumerating what currently sends it. For the channel that check is small — its entire write surface is two calls, one of which has no body — so there is no excuse for skipping it.

Hosted schema mirrors

The ac repository maintains its own copy of the OSS schemas. The cloud's migration_paths.py points at backend/src/aweb_cloud/migrations/aweb/ and migrations/server/ — NOT at the OSS package's migrations in the installed .venv. So when an OSS release adds or alters a schema the cloud uses, the cloud needs a paired mirror migration with a matching ALTER/CREATE.

The migrations to mirror can live in DIFFERENT OSS tree subdirectories within the same release. Easy to miss the second one when walking commit by commit:

  • awid/src/awid_service/migrations/*.sql → mirror in cloud as migrations/aweb/.
  • server/src/aweb/migrations/aweb/*.sql → also mirror in cloud as migrations/aweb/ (same target dir, different OSS source dir).

When reviewing a cross-repo bundle, grep ALL OSS migration trees touched in the bundle, not just the first one you find. Pattern-blindness on the second mirror is the failure mode.

Each mirror file should be a one-statement ALTER/CREATE matching the OSS content, with a header comment naming the OSS source path so the lineage is explicit.

Example: aweb-aaje (proxy auth team_id format)

  1. OSS: changed X-Team-ID validation from UUID to colon-form, deleted _resolve_proxy_team_id (cde8889, 0fbe3d9, 78794ff)
  2. Released: aweb 1.10.1
  3. Hosted repo: pinned 1.10.1 and changed the bridge to send colon-form (2761d0a5, 1f6e4797)
  4. Both deploy together in the cloud Docker image

Notes

  • The hosted ac repo is cloned at ../ac relative to the aweb workspace.
  • Ownership and review routing live in the active team instructions and aw workspace status; do not rely on names written here.

© awebai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/cross-repo-change of awebai/aweb.

Open the folder on GitHubat commit 3fbb43c

Compare with similar skills

Cross Repo Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross Repo Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross Repo Change this skillawebai/aweb115—~1.5kAutomated safety check: PassMIT
Agent Adaptive Coordinatorruvnet/ruflo74k2 repos~4kAutomated safety check: PassMIT
Agent Consensus Coordinatorruvnet/ruflo74k2 repos~3.2kAutomated safety check: PassMIT
Agent Hierarchical Coordinatorruvnet/ruflo74k2 repos~2.8kAutomated safety check: PassMIT
Agent Memory Coordinatorruvnet/ruflo74k2 repos~1.2kAutomated safety check: PassMIT
Agent Mesh Coordinatorruvnet/ruflo74k2 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • Agent Adaptive Coordinator

    ruvnet/ruflo

    Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator

    74k GitHub starsUsed in 2 repos~4k tokens
    Data & AnalyticsAuto-check passed

  • Agent Consensus Coordinator

    ruvnet/ruflo

    Agent skill for consensus-coordinator - invoke with $agent-consensus-coordinator

    74k GitHub starsUsed in 2 repos~3.2k tokens
    Agent WorkflowsAuto-check passed

  • Agent Hierarchical Coordinator

    ruvnet/ruflo

    Agent skill for hierarchical-coordinator - invoke with $agent-hierarchical-coordinator

    74k GitHub starsUsed in 2 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Agent Memory Coordinator

    ruvnet/ruflo

    Agent skill for memory-coordinator - invoke with $agent-memory-coordinator

    74k GitHub starsUsed in 2 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Agent Mesh Coordinator

    ruvnet/ruflo

    Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator

    74k GitHub starsUsed in 2 repos~3.2k tokens
    Agent WorkflowsAuto-check passed

  • Agent Queen Coordinator

    ruvnet/ruflo

    Agent skill for queen-coordinator - invoke with $agent-queen-coordinator

    74k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed

More from awebai/aweb

All 17 skills in this repo

  • Legacy aweb Bootstrap Recovery

    awebai/aweb

    Recognizes old aweb bootstrap-era `agents/` directories and migrates them to current team and identity primitives, since the old command family is retired.

    115 GitHub stars~701 tokensUpdated today
    Auto-check passed

  • aweb Team Coordination

    awebai/aweb

    Guides decisions for agents working in an aweb team: when to check shared state, claim tasks, take locks, read team roles and instructions, and open separate worktrees.

    115 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • aweb Messaging

    awebai/aweb

    Guides how an agent reads and responds to aweb mail and chat events, choosing between asynchronous mail and synchronous chat and respecting sender verification and encryption boundaries.

    115 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Aweb Team Membership

    awebai/aweb

    This skill should be used when joining or being added to an aweb team, picking the correct invite/add-member path for the team's authority model (hosted vs BYOT), accepting invites, fetching team…

    115 GitHub stars~5.4k tokensUpdated today
    Auto-check passed

  • Folio Template Documents

    awebai/aweb

    Creates or appends a folio document from the built-in pitch, memo or metrics templates by sending schema-checked slots that folio renders to Markdown.

    115 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Present To Human

    awebai/aweb

    A skill your agent uses when an agent needs to show a human an folio document: mint a document-bound capability link with POST /v1/present, open the returned URL for the human, print it as fallback…

    115 GitHub stars~590 tokensUpdated today
    Auto-check passed

Questions about Cross Repo Change

What does Cross Repo Change do?

Coordinate changes that touch both the aweb OSS repo and the hosted ac repo. Cross Repo Change is an agent skill from awebai/aweb. Coordinate changes that touch both the aweb OSS repo and the hosted ac repo.

How do I install Cross Repo Change in Claude Code?

Run `npx skills add awebai/aweb --skill cross-repo-change -a claude-code`. Or copy the skill folder (.claude/skills/cross-repo-change in awebai/aweb) into .claude/skills/cross-repo-change in your project. Claude Code loads it when a task matches its description.

How do I install Cross Repo Change in Codex?

Run `npx skills add awebai/aweb --skill cross-repo-change -a codex`. Or copy the skill folder (.claude/skills/cross-repo-change in awebai/aweb) into .agents/skills/cross-repo-change in your project. Codex loads it when a task matches its description.

Can I use Cross Repo Change in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add awebai/aweb --skill cross-repo-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-repo-change, .gemini/skills/cross-repo-change, .github/skills/cross-repo-change and .opencode/skills/cross-repo-change in your project.

What does Cross Repo Change need to run?

Going by SKILL.md and its folder, Cross Repo Change needs the command-line tools its instructions call (make and npm). Our summary lists: Docker.

Does Cross Repo Change access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cross Repo Change safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross Repo Change use?

Cross Repo Change is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Repo Change use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross Repo Change?

Skills that share tags, products or a category with Cross Repo Change: Agent Adaptive Coordinator (ruvnet/ruflo, 74k stars), Agent Consensus Coordinator (ruvnet/ruflo, 74k stars), Agent Hierarchical Coordinator (ruvnet/ruflo, 74k stars) and Agent Memory Coordinator (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Repo Change?

awebai (a GitHub organization) maintains it in awebai/aweb, which has 115 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 2026.

Source: awebai/aweb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.