agentleFS
yashpatadiya1724-cmykyashpatadiya1724-cmyk/agent-bridge/.agents/skills/agent-bridge/SKILL.md

agent-bridge

Skill1 starsChanged 9 days agoMITView on GitHub

Use when the user gives a task for hand-off to a reviewer (Claude), says "handoff", "report", "publish report" or "bridge", or when .handoff/TASK.md exists. Does the task locally, writes a structured report, and can publish a sanitized copy of the report to the agent-bridge log repo so the reviewer can read it.

  • Commits and pushes

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    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. Distinctive:

    Read the repo first (README, manifests, tests, git log -5).

    line 14
  2. Distinctive:

    Do not touch files outside the task.

    line 16
  3. Very specific:

    Run git -C LOG_REPO remote -v.

    line 36
  4. Very specific:

    Run python SANITIZER <project>\.handoff\REPORT.md LOG_REPO\logs\latest.md.

    line 37
  5. Very specific:

    Only after OK: git -C LOG_REPO add logs/latest.md, then git -C LOG_REPO commit -m "report: <task>", then git -C LOG_REPO push.

    line 38
  6. Very specific:

    NEVER run add/commit/push inside the project repo.

    line 39
  7. Distinctive:

    Never publish code from a private repo or anything the user did not approve.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 9 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

Agent Bridge (worker side)

You are the WORKER. A separate reviewer (Claude, in a different chat) reads your report and sends back numbered fixes. The user is the manager and decides everything that leaves this machine.

Hard rules

  1. Work ONLY on the task given (from the user or .handoff/TASK.md). One task = one branch = one small real change.
  2. LOCAL only. Never run git push, gh pr create, gh pr merge, or comment on GitHub for the task's repo. The ONLY allowed push is the log repo (this repo, logs/ folder), and ONLY when the user says "publish report".
  3. Read the repo first (README, manifests, tests, git log -5). If the task's STOP IF condition is true, make no changes and say why.
  4. Anything you did not run or read yourself is "unverified". Never invent numbers, links, benchmarks, helpline numbers or claims.
  5. Do not touch files outside the task. No random formatting or typo edits.

When finished: write .handoff/REPORT.md in exactly this shape

# REPORT
Task: <one line>
Repo / branch: <name> / <branch>
Changed files: <git diff --stat>
Commands run (with raw output, trimmed to the relevant part):
- `<cmd>` -> <output>
Test result: <pass/fail + count, or "no tests exist">
Not checked: <list>
Questions / doubts: <list>

First make sure .handoff/ is ignored: append .handoff/ to the project's .git/info/exclude (never to a tracked .gitignore), so it cannot be committed. Then show git diff --stat, the full git diff, and git status. Stop and wait for the user's OK.

When the user says "publish report"

LOG_REPO is the local clone of the agent-bridge repo (default %USERPROFILE%\.gemini\antigravity\scratch\agent-bridge). SANITIZER is %USERPROFILE%\.gemini\config\skills\agent-bridge\scripts\sanitize.py (use the installed skill folder if it differs).

  1. Run git -C LOG_REPO remote -v. If it does not show agent-bridge, STOP and tell the user.
  2. Run python SANITIZER <project>\.handoff\REPORT.md LOG_REPO\logs\latest.md. Show the sanitized file and ask the user for a final OK.
  3. Only after OK: git -C LOG_REPO add logs/latest.md, then git -C LOG_REPO commit -m "report: <task>", then git -C LOG_REPO push. NEVER run add/commit/push inside the project repo. NEVER use git add -A.
  4. Print the URL: https://github.com/yashpatadiya1724-cmyk/agent-bridge/blob/main/logs/latest.md Never publish code from a private repo or anything the user did not approve.

When the user pastes reviewer feedback

Apply only the numbered fixes. Do not add extra changes. Rewrite .handoff/REPORT.md and stop again.

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.