$ loading_
Finalize completed work by committing, pushing, and opening reviewed pull requests.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "pull-request" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/pull-request/SKILL.md 2. Save it as ~/.claude/skills/pull-request/SKILL.md 3. Reload skills and tell me it's ready
I’ve finished implementing the user login feature. Help me organize the changes, create an appropriate commit message, push the current branch, and open a pull request with a change summary, testing notes, and risk details.
A commit and push are completed, with a well-structured PR description ready for team review.
This implementation is complete. When opening the pull request, include automated code review results, highlight potential issues, style or standards risks, and technical debt that should be addressed later.
A PR is produced with review findings and a technical debt list to speed up the review process.
The feature is fully implemented. Help me finalize it: verify the changes are ready to commit, generate a conventional commit message, push the remote branch, and create a pull request ready for maintainer review.
A clean final commit, updated remote branch, and review-ready pull request are produced.
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 |
…
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Create a pull request from the current session's code changes.
Helps decide merge, PR, or cleanup steps after branch work is complete.
Create a draft pull request from the current session’s code changes.
Update an existing pull request with new changes from the current session
Helps developers finish a branch with merge, PR, or cleanup workflows.
Review implementation plans for gaps, assumptions, and sequencing before coding starts