npx skills add https://github.com/boshu2/agentops --skill pr-implement基于 Fork 的开源贡献实现,强制执行隔离检查。
通过 Fork 隔离执行贡献计划。在实施前和实施期间运行隔离检查,确保 PR 干净且专注。
输入 : 来自 $pr-plan 的计划产物或仓库 URL
使用时机 :
$pr-plan 之后不应使用的情况 :
$implement)$pr-plan)-1. 先前工作检查 -> 阻塞性: 检查是否存在冲突的 PR
0. 输入发现 -> 查找计划产物或仓库
1. Fork 设置 -> 确保 Fork 存在且为最新状态
2. 工作树创建 -> 创建隔离的工作树
3. 隔离预检查 -> 如果存在混合关注点则阻塞
4. 实施 -> 执行计划
5. 隔离后检查 -> 如果范围蔓延则阻塞
6. 提交准备 -> 使用正确的提交类型暂存
7. 交接 -> 准备进行 $pr-prep
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
# 搜索关于此主题的开放 PR
gh pr list -R <owner/repo> --state open --search "<topic>" --limit 10
# 检查目标 issue 状态
gh issue view <issue-number> -R <repo> --json state,assignees
| 发现情况 | 操作 |
|---|---|
| 存在开放 PR | 协调或等待 |
| Issue 已分配 | 协调或寻找替代方案 |
| 无冲突工作 | 继续 |
# 提交类型分析
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u
# 文件主题分析
git diff --name-only main..HEAD | cut -d'/' -f1-2 | sort -u
| 检查项 | 通过标准 |
|---|---|
| 单一提交类型 | 0 或 1 个前缀 |
| 主题性文件 | 全部符合计划范围 |
| 分支新鲜度 | 基于最近的 main 分支 |
如果预检查失败,请勿继续。
| 指导原则 | 原因 |
|---|---|
| 单一关注点 | 每次提交 = 一个逻辑变更 |
| 遵循惯例 | 严格遵循项目风格 |
| 增量测试 | 每次变更后运行测试 |
git commit -m "type(scope): 简要描述
如果需要,提供更长的解释。
关联: #issue-number"
# 提交类型分析
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u
# 摘要统计
git diff --stat main..HEAD
| 检查项 | 通过标准 |
|---|---|
| 单一提交类型 | 所有提交共享相同前缀 |
| 主题性文件 | 所有文件都与 PR 范围相关 |
| 原子化范围 | 可以用一句话解释 |
实施完成。隔离检查已通过。
分支: origin/$BRANCH_NAME
提交: N 次提交,+X/-Y 行
下一步: $pr-prep
| 禁止操作 | 替代做法 |
|---|---|
| 跳过隔离预检查 | 首先运行阶段 3 |
| 跳过隔离后检查 | 推送前运行阶段 5 |
| 在提交中混合关注点 | 每个 PR 使用一种类型前缀 |
| 无计划实施 | 先运行 $pr-plan |
用户说: "使用隔离检查来实施这个外部 PR 计划。"
会发生什么:
用户说: "在我准备 PR 之前,确保这个分支仍然是单一目的的。"
会发生什么:
$pr-prep。| 问题 | 原因 | 解决方案 |
|---|---|---|
| 隔离检查失败 | 分支上存在无关变更 | 将无关编辑移动到单独的分支/PR |
| 提交混合关注点 | 实施偏离了计划 | 按关注点重新拆分提交并重新验证 |
| 范围持续扩大 | 计划中的边界定义不明确 | 重新锚定到 超出范围 并停止额外变更 |
| 难以交接 | 缺少摘要/测试上下文 | 添加简洁的变更摘要和验证说明 |
每周安装量
129
仓库
GitHub 星标数
198
首次出现
2026年2月18日
安全审计
安装于
opencode129
gemini-cli125
github-copilot125
codex125
kimi-cli125
amp125
Fork-based implementation for open source contributions with mandatory isolation check.
Execute a contribution plan with fork isolation. Ensures PRs are clean and focused by running isolation checks before and during implementation.
Input : Plan artifact from $pr-plan or repo URL
When to Use :
$pr-planWhen NOT to Use :
$implement)$pr-plan first)-1. Prior Work Check -> BLOCKING: Check for competing PRs
0. Input Discovery -> Find plan artifact or repo
1. Fork Setup -> Ensure fork exists and is current
2. Worktree Creation -> Create isolated worktree
3. Isolation Pre-Check -> BLOCK if mixed concerns
4. Implementation -> Execute plan
5. Isolation Post-Check -> BLOCK if scope creep
6. Commit Preparation -> Stage with proper commit type
7. Handoff -> Ready for $pr-prep
# Search for open PRs on this topic
gh pr list -R <owner/repo> --state open --search "<topic>" --limit 10
# Check target issue status
gh issue view <issue-number> -R <repo> --json state,assignees
| Finding | Action |
|---|---|
| Open PR exists | Coordinate or wait |
| Issue assigned | Coordinate or find alternative |
| No competing work | Proceed |
# Commit type analysis
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u
# File theme analysis
git diff --name-only main..HEAD | cut -d'/' -f1-2 | sort -u
| Check | Pass Criteria |
|---|---|
| Single commit type | 0 or 1 prefix |
| Thematic files | All match plan scope |
| Branch fresh | Based on recent main |
DO NOT PROCEED IF PRE-CHECK FAILS.
| Guideline | Why |
|---|---|
| Single concern | Each commit = one logical change |
| Match conventions | Follow project style exactly |
| Test incrementally | Run tests after each change |
git commit -m "type(scope): brief description
Longer explanation if needed.
Related: #issue-number"
# Commit type analysis
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u
# Summary stats
git diff --stat main..HEAD
| Check | Pass Criteria |
|---|---|
| Single commit type | All commits share same prefix |
| Thematic files | All files relate to PR scope |
| Atomic scope | Can explain in one sentence |
Implementation complete. Isolation checks passed.
Branch: origin/$BRANCH_NAME
Commits: N commits, +X/-Y lines
Next step: $pr-prep
| DON'T | DO INSTEAD |
|---|---|
| Skip isolation pre-check | Run Phase 3 FIRST |
| Skip isolation post-check | Run Phase 5 before push |
| Mix concerns in commits | One type prefix per PR |
| Implement without plan | Run $pr-plan first |
User says: "Implement this external PR plan with isolation checks."
What happens:
User says: "Make sure this branch is still single-purpose before I prep the PR."
What happens:
$pr-prep.| Problem | Cause | Solution |
|---|---|---|
| Isolation check fails | Unrelated changes on branch | Move unrelated edits to separate branch/PR |
| Commits mix concerns | Implementation drifted from plan | Re-split commits by concern and revalidate |
| Scope keeps expanding | Weak boundaries in plan | Re-anchor to Out of Scope and stop additional changes |
| Hard to hand off | Missing summary/test context | Add concise change summary and verification notes |
Weekly Installs
129
Repository
GitHub Stars
198
First Seen
Feb 18, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode129
gemini-cli125
github-copilot125
codex125
kimi-cli125
amp125
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
152,900 周安装