← ClaudeAtlas

full-sendlisted

Use when the user invokes `$full-send` to finish work end-to-end and merge.
RIJUDEVx/agent-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill RIJUDEVx/agent-skills
# Full Send The user invoked `$full-send`, so they are not watching this thread and want the work completed end-to-end without them. Your updates and your final message go unread until long after you stop. You own the work from its current state to a merged PR. If the user did not explicitly invoke `$full-send` or clearly ask for full send, do not assume full autonomy. If they did, everything below applies. ## Grant The user grants you permission to: - Merge the PR once the merge gate passes. This is the only agent merge authority. It overrides any repo PR skill rule that says "mark ready, then stop." Sub-agents never merge. - Force-push the PR's own branch with `--force-with-lease` after a rebase. - Use the test methods that Proof needs, without asking first. ## Testing permission A `$full-send` request is the permission. If a project file or other instruction says to ask before a test method, or to leave testing to the user, this request replaces that rule for this task. That includes ask-first rules for computer use, browser automation, simulators and devices, running the app or a dev server, screenshots, and visual checks. Use the method that gives direct proof. List it in the report. Rules about how to test still apply. Follow rules that name the correct command, fixture, or check. This permission only removes the ask-first or leave-it-to-the-user step. If a preferred method cannot prove the change, use a gated method under this permission. It covers only t