agentleFS
Sign inStart free
dadwadw233dadwadw233/team-collab-skills/skills/gate/SKILL.md

gate

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Use when the user invokes `$gate`, asks whether a PR/merge is ready, asks to gate-check or merge-gate a multi-agent task, or asks "can this merge?".

  • Installs packages

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use new, build and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 5 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 8 projects that use this

  • VercelSkill

    investigate

    Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Follow the installed team-collab-protocol skill and its references/gate-check.md flow.

    line 21
  2. Very specific:

    Before running any CLI command, check command -v team-collab.

    line 22
  3. Distinctive:

    Do not merge anything yourself.

    line 30
  4. Very specific:

    If a future Codex version supports custom slash commands and /gate reaches the model as plain user text, handle it exactly the same way as …

    line 34

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Team Collab Gate

This is a Codex-friendly command wrapper for the multi-agent merge gate check. Codex does not currently support arbitrary custom top-level slash commands like /gate, so the supported Codex entry point is:

$gate --pr <number>

What this does

The gate runs the pre-merge checks for a multi-agent task: agent sign-off, independent review, dependencies merged, owned-files scope, human-gated patterns, claim integrity, and truth-source freshness. $gate is the human→coordinator shortcut so you can ask "can this merge?" in one line instead of typing the full CLI.

Required behavior

  1. Follow the installed team-collab-protocol skill and its references/gate-check.md flow. If the protocol skill is not available in the current session, read ~/.codex/skills/team-collab-protocol/SKILL.md; if that file is missing, stop and tell the user to run team-collab install-skills --agent codex --force.
  2. Before running any CLI command, check command -v team-collab. If missing, stop and tell the user to install the CLI with npm install -g @embodot/collab@latest, then refresh skills with team-collab install-skills --agent codex --force if needed.
  3. Parse a --pr <number> (or --pr=<number>) from the text after $gate. If the user said something like $gate 42 or $gate PR42, treat the number as the PR. If no PR is given, ask which PR.
  4. Infer the wave from the current working directory if possible (multi-agent/<slug>/ subtree); otherwise ask, or pass it through as --wave <slug>.
  5. Run the gate:
    team-collab multi-agent gate --pr <number> [--wave <slug>]
  6. Report the result clearly to the user. Exit code 0 means the task may merge (possibly with warnings); exit code 5 means the gate found a blocking issue — summarize which check failed and point to the relevant references/gate-check.md section. Exit code 2 means a config/wave problem; 4 means a git/network read failure.
  7. Do not merge anything yourself. The gate only checks; merging is a separate human or coordinator decision.

Compatibility note

If a future Codex version supports custom slash commands and /gate reaches the model as plain user text, handle it exactly the same way as $gate.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free