$ loading_
在实现完成后协助提交代码、推送分支并发起拉取请求与自动审查。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "pull-request" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/pull-request/SKILL.md 2. 保存为 ~/.claude/skills/pull-request/SKILL.md 3. 装好后重载技能，告诉我可以用了
我已经完成用户登录功能开发，请帮我整理变更、生成合适的提交信息，推送当前分支，并创建一个包含变更摘要、测试说明和风险说明的 Pull Request。
完成提交与推送，并生成结构清晰的 PR 描述，便于团队审核。
这个实现已经完成，请在发起 Pull Request 时附带自动代码审查结果，指出潜在问题、规范风险和需要后续处理的技术债。
生成带审查结论和技术债清单的 PR 内容，帮助更快进入评审流程。
当前功能已经开发完成，请帮我做最终整理：检查改动是否适合提交、生成规范提交说明、推送远程分支，并创建可直接交给维护者审核的 Pull Request。
得到规范的最终提交、远程分支更新，以及可直接审核的 PR。
Use read/changes to list source control changes. In addition:
git status
git diff --stat
If there are uncommitted changes, use the git-commit skill to commit.
Before pushing or creating a PR, verify the current branch is not the integration branch:
CURRENT_BRANCH=$(git branch --show-current)
Resolve the integration branch in this order:
Integration Branch from .memory/git-config.md (if it exists)git symbolic-ref refs/remotes/origin/HEADmain, master, or developIf the current branch matches the integration branch, stop and offer recovery:
You are on `[branch]`, which is the integration branch. A PR cannot be created from the integration branch to itself, and pushing directly bypasses code review.
[B] Create a feature branch from the current commit(s) and open a PR (recommended)
[P] Push directly to [branch] (not recommended, bypasses code review)
If the user chooses [B]:
| Current state | Recovery action |
|---|---|
| Committed locally, not pushed | Create feature branch at HEAD, then reset integration branch to origin/[branch]: git branch <feature-branch>, git reset --hard origin/[branch], git checkout <feature-branch>. Confirm with the user before resetting. |
| Already pushed to integration branch | Create feature branch from the offending commit(s), push it, offer to revert the commit on the integration branch, then open PR from the feature branch. |
If the user chooses [P], proceed with the push. Log the override decision.
This guard applies to both the PR creation path and the Push Only path below.
If the automated review was already executed by devsquad.implement (step 9 of the orchestration flow), do not re-execute review. Use the result already obtained.
Implementation completed and committed.
Would you like me to open a Pull Request?
[Y] Yes, open PR
[R] Review implementation before PR (recommended for medium/high impact)
[N] No, just push
If the user chooses [R] and the automated review was already executed, present the existing result instead of re-executing.
The type of review depends on the task's impact. Security review is delegated to devsquad.review when it is invoked — both never run separately.
Triggers (any of):
Execute devsquad.review as a sub-agent. Pass the feature, task, and modified files.
High impact task. Running independent review...
After sub-agent result:
When devsquad.review is not invoked automatically, assess if a security review is needed by evaluating the security triggers defined in devsquad.security (Authentication/Authorization, Sensitive data, External input, Persistence, Integrations).
If a trigger is detected, execute devsquad.security as a sub-agent in code mode.
After the result, present the verdict (PASSED / PASSED_WITH_FINDINGS / FAILED) following the same format above.
If no trigger is detected, proceed with PR.
| Impact | Review | Security |
|---|---|---|
| High | devsquad.review (auto) | Delegated by devsquad.review internally |
| Medium/Low + security trigger | No (available via [R]) | devsquad.security direct |
| Medium/Low without trigger | No (available via [R]) | No |
…
帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。
帮助用户把当前会话中的新代码变更更新到已有拉取请求中