跳到正文
cccskills
免费在 GitHub 公开

sol-loop

Review code changes with GPT Sol in a controlled loop before or after opening a pull request. Track findings by severity, make minimal fixes, rerun checks, and continue only while meaningful issues remain, so the review stays focused on the requested change.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when the user says "sol loop".

t3dotgg/tstack星标 1,743(GitHub 1,743 + cccskills 0)

实测评分 未实测

查看安装方法

适用场景

  • Reviewing a code change before opening a pull request
  • Checking fixes against findings from an earlier review
  • Keeping a security or permissions review focused

包含的文件(1)

  • SKILL.md5.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

sol-loop

This is a workflow for making your code changes more correct before (or sometimes after) filing a pull request. tl;dr - use OpenAI's GPT Sol to review your code in a loop.

Make the most minimal possible changes to appease the Sol reviewers. Be careful of scope creep and don't be scared to push back.

Budget

  • Default: 3 rounds total. Round 1 is full. Later rounds check only changed code and open findings.
  • Extend to 5 only for security, permissions, auth, data loss, or state/concurrency, while a blocker or should stays open with evidence. Or when the user asks.
  • Stop early if a round returns only nits. Declined nits and comment, doc, or format-only fixes need no new round.
  • One reviewer only. Sol must not start subagents or reviewers.
  • Keep a ledger: id, severity, outcome, usage if returned. Never guess it.

1. Scope

Run git status --short. Do not stash, discard, or include unrelated changes. Limit review to the change paths if they separate cleanly. Otherwise stop and ask.

Find the base after git fetch origin:

  • PR: gh pr view <n> --json baseRefName,headRefOid. Check out the branch only if clean. Confirm HEAD is the PR head, or ahead only by this change. Base: git merge-base HEAD origin/<baseRefName>.
  • Local: git merge-base HEAD origin/<default-branch>. No remote: a base the user names, or HEAD for uncommitted changes only.

The change is base to working tree in those paths, with untracked files. Use one diff command all rounds. State intent and out-of-scope in 1-2 sentences. Run covering checks. Do not send code this change breaks. Note missing or pre-failing checks in the brief.

2. Start Sol

In T3, call orchestrator_capabilities. Pick the latest Sol unless the user named a version. Do not hardcode an ID. Record provider, model, and effort only if exposed. Use delegate_task every round (role: "review", mode: "async"). Save taskId. New clientRequestId per round. childThreadId is storage, not the next target. Do not use t3_thread_send, create_threads, or t3_thread_launch for review.

If T3 tools are not listed, try one direct capability call. Outside T3, use a native Sol subagent and keep its ID. In Claude Code, use a custom subagent only if it is set up to run Sol. If no route runs Sol, report the blocker. Do not substitute a model.

Do not edit scoped files while review runs. Wait for the notice. Do not poll or start a second reviewer. Timeout, error, or no reply is not approval. On failure, cancel, verify stop, restart with the ledger.

Round 1 brief (T3 children get no history):

Review only. Do not edit, commit, push, comment on PRs, or start subagents.
Repo: <abs path> Base: <sha> Intent: <intent> Out of scope: <scope> Checks: <results>
See: git diff <base> [-- <paths>]; git status --short (read untracked).
Read surrounding code. Find bugs, broken callers, mismatch with intent.
Skip style unless it hides a bug. Hold to the smallest change. Flag code,
tests, or guards the intent does not need. Other paths, rare cases, small
perf, extra compat: nits.
blocker = intended case wrong. should = real bug callers will hit, in intent. nit = rest.
Reply:
VERDICT: APPROVE or CHANGES
S1 [blocker|should|nit] <file>:<line> <claim>. Fix: <suggestion> (stable ids)

3. Answer findings

Check each finding and severity yourself. Another path, rare case, or small cost is a nit, whatever label it came with.

  • Agree: smallest fix. Prefer delete or narrow over new lock, cache, helper, or option. Fix the case that happened. Add one focused test that fails without the fix, if intent needs it.
  • Disagree: say why, with evidence (file:line, test, output).
  • Out of scope or nit: decline in one line. List as follow-up.

Update the ledger. Re-run checks and git diff --shortstat <base>. If review grew the diff, cut first. Do not agree just to end the loop.

4. Next round

Start one only if budget remains and a blocker or should is open, behavior code changed, or approval does not cover the current behavior diff. Use a fresh delegate_task in T3, or follow up the saved native ID. Send the round 1 brief, the ledger (fixed: / disagree: / declined: + evidence), the same base diff, and the change since last round. Tell Sol: open ids and changed code only. Mark each old id resolved or still open: <reason>.

5. Stop and ship

Agreed: APPROVE on the current behavior diff, no blocker or should open, no concern of your own. Stuck: an item stays disputed after two replies, or budget ends. Show both sides in 2-3 lines each. The user decides. Budget end is not approval.

Do not push during the loop. Push after agreement only if the user asked to push, ship, or update the PR. If you push to a PR, add above the model blurb:

Reviewed with sol-loop: <N> rounds with <model>. Sol verdict: approved.

Add on <effort> only if verified.

Report: rounds, model, what Sol changed, diff size before/after, fixed and declined findings with reasons, usage if exposed (else say not), pushed or not.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Monitor a pull request through reviews and CI checks, then respond to real failures and feedback. The skill helps determine when the latest changes meet the repository’s merge conditions; it reports readiness without merging unless the user asked for a merge.

中文简介正在准备中。当前显示英语简介。

  • Watching a PR until required checks and reviews are complete
  • Checking whether new review comments need code changes
  • Tracking CI failures and branch conflicts
t3dotgg/tstack17432026年10月27日 更新

council

免费

Get parallel feedback on a request from three delegates using models from different providers. The skill gathers their findings, summarizes agreements and disagreements, and suggests next steps; code reviews also include a score from each delegate.

中文简介正在准备中。当前显示英语简介。

  • Getting several perspectives on a proposed change
  • Reviewing code with three model providers
  • Summarizing reviewer disagreements before deciding next steps
t3dotgg/tstack17432026年10月27日 更新

file-pr

免费

Prepare and open a concise pull request by checking for an existing PR, reviewing the branch diff, and writing a clear title and problem-focused description. The skill also checks the submission text and attachments for secrets or private details.

中文简介正在准备中。当前显示英语简介。

  • Opening a pull request for completed work
  • Checking whether a branch already has a PR
  • Writing a clear PR title and description
t3dotgg/tstack17432026年10月27日 更新

full-send

免费

Carry a requested code change from implementation through direct proof, review, pull request updates, and merge when the required checks pass. The workflow also tracks review findings and asks the user only when progress is blocked or a decision is outside its permission.

中文简介正在准备中。当前显示英语简介。

  • Completing a code change through merge
  • Running checks and gathering evidence for a fix
  • Handling review feedback and CI failures on a pull request
t3dotgg/tstack17432026年10月27日 更新

full-stop

免费

Take a requested change through implementation, proof, review, and pull request readiness, then hand it back without merging. It follows the full-send workflow for testing and review, checks the live pull request state, and reports whether it is ready, awaiting approval, or blocked.

中文简介正在准备中。当前显示英语简介。

  • Preparing a pull request for the user to merge
  • Verifying a change and addressing review findings
  • Checking why a pull request is not yet ready
t3dotgg/tstack17432026年10月27日 更新

Format comments posted on GitHub on the user’s behalf with clear attribution, then review the full Markdown for private details before posting. The skill covers PR comments, inline reviews, replies, and explanations for resolving feedback.

中文简介正在准备中。当前显示英语简介。

  • Writing a reply to a pull request review
  • Adding an inline code review comment
  • Explaining why a bot finding is dismissed
t3dotgg/tstack17432026年10月27日 更新

查看 t3dotgg 的全部技能

报告此技能的问题