agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/full-send/SKILL.md

full-send

Skill4 starsChanged 10 days agoMITView on GitHub

Compatibility preset for author delivery through an authorized merge; full stop or --no-merge retains the merge decision.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use full-stop, leaving-pr-comments and 9 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.
  • Nexus-Organization-InfosecSkill

    full-stop

    Shut down the Full Control phone-bridge completely — end Claude's watch loop, stop the bridge server (server.py started via ensure_server.ps1), and mark Claude offline in the app. Use whenever the user invokes /full-stop or says "stop full control", "stop the watch loop", "shut down the bridge/server", or "stop the ps1". Counterpart of [[full-control]], which starts everything.

    Also in 11 projects that use this

  • scottwaterSkill

    leaving-pr-comments

    Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.

    Also in 8 projects that use this

  • scottwaterSkill

    sol-loop

    Review a change with GPT Sol in a loop until both agents agree. Use when the user says sol loop, or when another skill asks for a Sol review.

    Also in 8 projects that use this

  • assisjpSkill

    file-pr

    Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.

    Also in 8 projects that use this

  • assisjpSkill

    takeover

    Take over an existing branch, pull request, worktree, or agent handoff while preserving the original goal, contributor credit, and concurrent work. Use when the user asks to take over, finish, rescue, or continue someone else's implementation. Do not use to replace a clear request to start new work.

    Also in 3 projects that use this

  • owidSkill

    babysit-pr

    Spawn a background agent that babysits an open PR — triggers a Codex review, watches CI, judges and fixes valid findings, replies to and resolves review threads, and loops to a cap. Never merges. Trigger when the user asks to "babysit the PR", "ask for codex review(s) and watch CI", or after pushing a substantial chunk to a PR branch.

    Also in 8 projects that use this

  • +1 more from scottwater

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read and run the shared workflow, not a second full-send implementation.

    line 17
  2. Distinctive:

    Read tstack composition and its upstream proof guidance without changing this owner, adding implicit reviewers or broadening permissions.

    line 22

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

An explicit full send <task or PR> selects the author delivery workflow and authorizes fixes, commit, push, PR and a policy-compliant merge of that one unambiguous deliverable. Automatic PR maintenance handles CI/review/base issues and uses host-authorized wakes for pending events; report genuine blockers. Discussing this skill is not an invocation.

Earlier stops win: local, no push, draft only, PR-ready, full stop or --no-merge narrow the endpoint. Babysitting alone never grants merge permission. Resolve target/owned worktree, reuse its PR and keep its branch checked out in Conductor. Ask only if the target is ambiguous or an owner-reserved decision blocks it.

Read and run the shared workflow, not a second full-send implementation. For unfinished code, load development-lifecycle; existing PRs start from their current evidence. Use REFERENCE.md only for its requested checkpoint, notification, resume or explicitly delegated review branch. No automatic model switch or agents.

Read tstack composition and its upstream proof guidance without changing this owner, adding implicit reviewers or broadening permissions.

The shared workflow selects native context for authorized monitoring; keep one delivery loop, not a separate T3 workflow.

Inspiration and research limits: SOURCES.md. Local delivery composes a licensed tstack snapshot; it is not an upstream endorsement.

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