Skip to main content

full-stop

Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.

ソース情報

リポジトリ
t3dotgg/tstack
ソースの最終更新活動
2026年10月27日 08:27
検出された SKILL.md の言語
英語
スター
3,296
フォーク
248

full-stop: Full Send, Stop Before Merge

Follows the full-send workflow through a merge-ready PR, including Proof testing permission, but never merges.

Uses

Trigger when the user says full stop (even as emphatic closing punctuation).

Prerequisites

Same tooling as full-send except merge/auto-merge is forbidden.

How to use

Run full-send’s work, proof, review, and babysitting; leave the PR ready for the user to merge.

Limitations

May commit, push, rebase, and --force-with-lease; never merge or enable auto-merge.

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー
2 ファイル

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
full-stop
description
Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.
# Full Stop Do the same work as `full-send`, but stop with the PR ready for the user to merge. Never merge it. Read [full-send](../full-send/SKILL.md) and follow its workflow, proof rules, review, and babysitting steps. An explicit "full stop" request authorizes that work without a separate "full send" request. That includes full-send's testing permission. A "full stop" request is the permission for the test methods Proof needs, even when a project file says to ask first, for example before computer use. Use those methods directly. Its merge permission does not apply. The overrides below take precedence. ## No merging You may commit, push, rebase, fix conflicts, and use `--force-with-lease` on this task's branch. Never merge, enable auto-merge, enter a merge queue, push to the default branch, bypass branch protection, or delegate those actions. Disable existing auto-merge and remove the PR from any merge queue before work begins; check again before each push. Report these changes. If you cannot prevent automatic merging, report the blocker before proceeding. ## Stop at the gate Use full-send's merge gate as the readiness check. Replace its merge and final report steps with a handoff. Proof and review must cover the final diff; recheck behavior changes and meaningful conflict fixes before handoff. Fetch the target branch and check the live PR's head, base, checks, reviews, and mergeability. Confirm it is open, not a draft, and not set to merge without the user. If someone else merged it, report that instead. - **Ready to merge:** the merge gate passes. Leave the PR open and unmerged. - **Waiting for required approval:** only human approval remains. Confirm that this is the actual blocker. - **Blocked:** explain what prevents readiness, what you tried, and what is needed. Follow full-send's rules for asking the user. In T3 Code, call `unwatch_pull_request` before the handoff or a question. Report the PR link, final head, verdict, proof, reviewer outcome, and remaining risks. State whether the PR is still open and unmerged.
GitHubで見る