审查
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 安全
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
确定当前分支: `git branch --show-current` 检查 PR 是否已存在: `gh pr list --head <branch> --json number,url` 如果不存在 PR,则创建一个:记下 PR 编号。
查找最新的工作流程运行:`gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId` 如果运行正在进行,请观看:`gh run watch <id>` 如果失败:获取失败日志:`gh run view <id> --log-failed` 诊断并修复问题。
等待 60 秒,让 SonarCloud 分析传播。使用`get_project_quality_gate_status`和项目密钥`Brad-Edwards_aptl`检查质量门。使用`search_sonar_issues_in_projects`查找当前分支上的新问题。如果发现问题:修复它们。
重要:您必须使用技能工具来调用内置审核技能。将 dev 合并到当前分支:`git fetch origin dev && git merge origin/dev` 如果存在合并冲突,请解决它们,提交并推送。使用`skill="review"`调用技能工具来调用真正的内置代码审查。审核完成后,修复其发现的所有问题。
重要:您必须使用技能工具来调用内置的安全审查技能。使用`skill="security-review"`调用技能工具来调用真正的内置安全审查。审核完成后,修复其发现的所有问题。与第四阶段相同的规则:修复所有内容,不推迟任何内容。修复后,确认所有问题均已得到解决。
如果在第 4-5 阶段进行了任何修复:`git add` 所有更改的文件。 `git commit -m "Fix code review and security review findings"` `git push` 重新运行第 2 阶段(CI 监视器)。
您不得合并 PR。你不能运行`gh pr merge`。用户评论并合并。发货过程中所做的所有更改的摘要 审核结果和已修复的内容 安全审核结果和已修复的内容 确认:CI 绿色,SonarCloud 通过,PR 已准备好供用户审核
# Ship Current Branch
Assumes code is already committed and pushed. Handles: PR creation, CI monitoring, SonarCloud, code review, security review, fixing all issues, and merging.
**IMPORTANT:** NEVER include Co-Authored-By, "Generated with Claude Code", or any Claude/AI attribution in commit messages, PR descriptions, or any other artifacts.
## Phase 1: Create PR
1. Determine the current branch: `git branch --show-current`
2. Check if a PR already exists: `gh pr list --head <branch> --json number,url`
3. If no PR exists, create one:
```
gh pr create --base dev --title "<concise title>" --body "<description>"
```
4. Note the PR number.
## Phase 2: CI Monitor
1. Find the latest workflow run: `gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId`
2. If the run is in progress, watch it: `gh run watch <id>`
3. If it failed:
- Get failed logs: `gh run view <id> --log-failed`
- Diagnose and fix the issue.
- `git add`, `git commit`, `git push`.
- Go back to step 1.
4. If it succeeded, proceed.
## Phase 3: SonarCloud Check
1. Wait 60 seconds for SonarCloud analysis to propagate.
2. Use `get_project_quality_gate_status` with project key `Brad-Edwards_aptl` to check the quality gate.
3. Use `search_sonar_issues_in_projects` to find new issues on the current branch.
4. If issues found:
- Fix them.
- `git add`, `git commit`, `git push`.
- Re-run Phase 2.
5. If clean, proceed.
## Phase 4: Code Review
**CRITICAL: You MUST use the Skill tool to invoke the built-in review skill.**
1. Merge dev into the current branch: `git fetch origin dev && git merge origin/dev`
2. If there are merge conflicts, resolve them, commit, and push.
3. Call the Skill tool with `skill="review"` to invoke the real built-in code review.
4. After the review completes, fix ALL issues it identified.
- Do NOT defer ANY issues.
- Do NOT categorize issues as "low priority" to avoid work.
- You are an LLM. You have no time constraints. Fix everything.
- The ONLY reason to stop and escalate to the user is if a fix requires
a significant architectural change touching 5+ files outside the
current feature scope.
5. After fixing, re-read all findings and confirm each one was addressed.
## Phase 5: Security Review
**CRITICAL: You MUST use the Skill tool to invoke the built-in security-review skill.**
1. Call the Skill tool with `skill="security-review"` to invoke the real built-in security review.
2. After the review completes, fix ALL issues it identified.
- Same rules as Phase 4: fix everything, defer nothing.
3. After fixing, confirm all findings were addressed.
## Phase 6: Final Commit & CI
If ANY fixes were made in Phases 4-5:
1. `git add` all changed files.
2. `git commit -m "Fix code review and security review findings"`
3. `git push`
4. Re-run Phase 2 (CI Monitor).
5. Re-run Phase 3 (SonarCloud).
## Phase 7: Report (DO NOT MERGE)
**You MUST NOT merge the PR. You MUST NOT run `gh pr merge`. The user reviews and merges.**
- Summary of all changes made during the ship process
- Review findings and what was fixed
- Security review findings and what was fixed
- Confirmation: CI green, SonarCloud passed, PR ready for user review
- PR URL
---
> Source: [Brad-Edwards/aptl](https://github.com/Brad-Edwards/aptl) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
按说明文件中的顺序排列。
第一阶段:创建公关
第 2 阶段:CI 监控
第 3 阶段:SonarCloud 检查
第四阶段:代码审查
第五阶段:安全审查
文件/命令 -> git branch --show-current · gh pr list --head <branch> --json number,url · gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId · gh run watch <id> · gh run view <id> --log-failed · git add · git commit · git push
内容校验值 -> 69ebf2b96acb
当前原文的自动摘译,尚未人工审校。
第四阶段:代码审查
重要:您必须使用技能工具来调用内置审核技能。将 dev 合并到当前分支:
git fetch origin dev && git merge origin/dev如果存在合并冲突,请解决它们,提交并推送。使用skill="review"调用Skill工具来调用真正的内置代码审查。审核完成后,修复其发现的所有问题。