nubjs/nub✦ 精选0°

implementation-thread

仓库创建 2026年6月4日最近提交 2 小时前SkillHot 收录 1 小时前
▸ 精选理由

适合工程团队把控从设计到合并的全流程交付节点。

这个 Skill 做什么

将单个任务端到端推进到经审查、CI 绿色且待合并的 PR。

把一个工程任务从策划到代码评审、CI 绿色并挂起为待合并 PR,单人负责贯穿整个流程直到交回人为止。适合需要端到端推进、保持上下文连续且要多人审查的重要变更。特点是有明确暂停点把需要人决策的问题抛上来,并能为设计和多视角审查临时产出小组。

▸ 展开 SKILL.md 英文原文

Take a single task or issue through the COMPLETE engineering workup — plan → review the plan → implement → review the implementation (multi-lens where the blast radius warrants) → open a PR → await CI → fix CI → check for and integrate external reviews → RETURN CONTROL before merge. Invoke (via the Skill tool) whenever the user says "implementation-thread", or asks to drive a task/issue all the way through to a held PR. The defining shape: the effort is owned end-to-end by ONE sub-agent (an L1) that spawns its OWN L2 sub-agents for design and multi-lens review, carries continuity across phases, and PAUSES — comes to rest to surface a question UP — whenever a decision the human owns arises. It returns control to the orchestrator BEFORE merging unless explicitly told "merge it" / "all the way through". This is NOT a fray skill (it governs how one implementation effort runs internally); it COMPOSES with fray — an implementation-thread is one fray thread.

开发编程实施流程PR 管理代码审查通用
3.9k
Stars
54
Forks
38
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/implementation-thread/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/implementation-thread/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# implementation-thread

The end-to-end workup for taking ONE task/issue from nothing to a reviewed, CI-green PR **held at the merge gate**. The unit is a single coherent change — not a campaign of many (that's fray).

## Scope gate — is this even an implementation-thread?

**This is the workup for a SUBSTANTIAL change.** A change confined to a file or two, whose correctness its own diff plus the pre-push loop demonstrates, does not get a design pass, an L2 fleet, or a multi-lens review — you write it, verify it, and open the PR. Invoking this machinery on a small fix costs more than the fix, and every L2 hop returns a claim you then have to re-verify.

Use the full shape when the change cro
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有