docs(ux): formalize build reminders and PR output links

This commit is contained in:
Keith Guerin
2026-03-27 21:06:34 -07:00
parent 2c0165e8f3
commit 659a05d4eb
2 changed files with 7 additions and 1 deletions
@@ -31,6 +31,12 @@ underlying "rigor."
3. **Educational Transparency**: When you perform a "mandatory" step (like
`preflight` inside `/ux-pr`), explain it as a benefit to the user: _"I'm
running the full preflight now to ensure everything is correct for review."_
4. **Build Reminders**: Whenever you finish implementing a feature, fix, or
update, you MUST remind the user to test their changes by running:
`npm run bundle; node bundle/gemini.js`.
5. **PR Output**: After successfully creating or updating a PR, you MUST
provide the GitHub PR link, the linked Issue link, and the `npx` command to
test the PR branch (e.g., `npx @google/gemini-cli@pr-<number>`).
## 🚨 Standard Operating Procedures (Agent Only)
@@ -133,7 +133,7 @@ If operating in a sibling worktree (e.g., `feature-xyz/`):
- **Action**: Use `git rebase -i` or `git reset --soft` to organize commits into these tiers. Ensure refactors are ALWAYS isolated from logic.
- **Push**: `git push origin HEAD --force-with-lease`.
- **Draft PR**: If creating a new PR, you MUST create it as a draft by default (e.g., `gh pr create --draft`).
- **MANDATORY FINAL OUTPUT**: You MUST provide the full, clickable **GitHub PR link** (e.g., `https://github.com/google-gemini/gemini-cli/pull/23487`) AND the **Issue URL** (e.g., `https://github.com/google-gemini/gemini-cli/issues/12345`) as the final output of this skill. This allows the user to immediately verify the update and track the associated task.
- **MANDATORY FINAL OUTPUT**: You MUST provide the full, clickable **GitHub PR link** (e.g., `https://github.com/google-gemini/gemini-cli/pull/23487`), the **Issue URL** (e.g., `https://github.com/google-gemini/gemini-cli/issues/12345`), AND the **npx command** to test the PR branch directly (e.g., `npx @google/gemini-cli@pr-<number>`) as the final output of this skill. This allows the user to immediately verify the update and track the associated task.
#### 10. CI Verification & Remediation Loop (The Slog)
- **Context**: Getting PRs ready for review is typically a "slog" due to CI checks failing in the GitHub environment even after passing local presubmit tests.