Complete A Manual Pull Request Loop

Click Prepare practice folder. Run its enter-folder command in your terminal, then keep that terminal in this folder.

Look forYour terminal is in the exact folder shown by preparation, on its practice branch.

Run these commands to read the task and note. Stop if the branch differs from the prepared practice branch or unexpected edits appear.

git status --short --branch
Get-Content -LiteralPath workspace/manual_task/README.md
Get-Content -LiteralPath workspace/manual_task/project-note.md

git status --short --branch
sed -n '1,160p' workspace/manual_task/README.md
sed -n '1,160p' workspace/manual_task/project-note.md

git status --short --branch
sed -n '1,160p' workspace/manual_task/README.md
sed -n '1,160p' workspace/manual_task/project-note.md

Look forThe branch starts with practice/. No modified file is listed. The task names project-note.md as the file to edit.

In VS Code, choose File > Open Folder and select the exact practice-folder path shown by the Passport. Open workspace/manual_task/project-note.md. Edit it yourself, without an AI agent.

Look forYour editor shows project-note.md inside the prepared practice folder.

In workspace/manual_task/project-note.md, add a ## Verification heading and one short sentence in your own words about reviewing the staged diff before publishing. Include the terms staged diff and review. Save only this file. Put the text in your editor, not the terminal.

## Verification

The staged diff must be reviewed before publishing.

Look forThe saved note has your heading and reminder. No other file has changed.

Read every added (+) and removed (-) line. Is this the change you intended? Fix anything unexpected in the editor before staging.

git status --short
git diff -- workspace/manual_task/project-note.md

git status --short
git diff -- workspace/manual_task/project-note.md

git status --short
git diff -- workspace/manual_task/project-note.md

Look forOnly workspace/manual_task/project-note.md is modified. Its diff shows your heading and reminder, without unrelated changes or private information.

Run the block to stage the note, then read the staged diff. Confirm every line before committing. If you edit again, stage and review the newer version.

git add -- workspace/manual_task/project-note.md
git diff --cached --check
git diff --cached

git add -- workspace/manual_task/project-note.md
git diff --cached --check
git diff --cached

git add -- workspace/manual_task/project-note.md
git diff --cached --check
git diff --cached

Look forThe staged diff contains only the intended note change. The whitespace check prints nothing when it passes.

Will your colleague see this new commit on GitHub? Think about that, then run the command.

git commit -m "docs(practice): explain staged diff review"

git commit -m "docs(practice): explain staged diff review"

git commit -m "docs(practice): explain staged diff review"

Look forGit prints a new commit with the subject docs(practice): explain staged diff review.

Which command shares your commit, and which asks for review? Run the prepared git push command, then its gh pr create command, one at a time. Keep --draft. Leave the PR open in draft; do not merge it.

Look forOne open draft PR proposes your practice branch to main. Opening it has not merged your change into main.

Run both commands to open your PR; the local Passport fills in your fork and branch. Do not run gh repo set-default. In Files changed, check that the reminder makes sense and the diff matches your reviewed edit.

gh pr status --repo {{fork_repository}}
gh pr view {{practice_branch}} --repo {{fork_repository}} --web

gh pr status --repo {{fork_repository}}
gh pr view {{practice_branch}} --repo {{fork_repository}} --web

gh pr status --repo {{fork_repository}}
gh pr view {{practice_branch}} --repo {{fork_repository}} --web

Look forYou are the author; your practice branch targets main. Only project-note.md changed, with your reviewed reminder and commit subject. Leave the PR open in draft; do not merge it.