Add Jules PR Manager Skill

[timothyfroehlich]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
pin-point	Ready	Preview, Comment	Jan 8, 2026 1:13am

[Copilot]

Pull request overview

This PR introduces a comprehensive Jules PR Manager skill for managing Google's Jules AI agent pull requests within the Gemini CLI environment. The PR adds two new agent skill documentation files and cleans up obsolete staging files, along with minor formatting fixes.

Key Changes:

• Adds Jules PR Manager skill with workflow automation, priority-based processing, and batch operations
• Adds Creating Skills guide following TDD principles for skill documentation
• Removes obsolete .github-staging/ CI workflow files (already activated)
• Adds .gemini/tmp/ to .gitignore for skill temporary files

Reviewed changes

Copilot reviewed 8 out of 10 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.gemini/skills/jules-pr-manager/SKILL.md	New skill defining workflows, priorities, and automation for managing Jules-created PRs
.gemini/skills/creating-skills/SKILL.md	New comprehensive guide for writing and testing agent skills using TDD methodology
docs/plans/update_creating_skills.md	Planning document for updating skill creation documentation for Gemini CLI compatibility
.github-staging/workflows/ci.yml	Removed obsolete CI workflow (already moved to .github/workflows/)
.github-staging/workflows/README.md	Removed obsolete staging README for CI workflow
.github-staging/README.md	Removed obsolete staging directory README
.gitignore	Added .gemini/tmp/ to ignore temporary skill processing files
.Jules/palette.md	Removed Palette agent journal file
src/lib/email/client.ts	Fixed indentation alignment in environment variable checks
src/components/ui/button.tsx	Reformatted interface declaration to single line

[timothyfroehlich]

Here's the state machine that I intended the skill to implement.

New PR (no labels) -> Perform vetting: Determine if it's a duplicate, if so, determine which PR to keep (Best implementation wins) and if there are changes from the duplicates that should be merged into the keeper. If so, post a review comment on the keeper requesting those changes be implemented in the keeper PR, set label to changes-requested on that PR. Close the non-keeper PRs. Then, if the current PR is not a duplicate, and does not have "vetted", perform a short review of the code and present a description of the PR and whether the Agent thinks it's a change worth making, with sufficient information that the User can make a determination about whether to move forward with the PR based solely on that information. If User says close then close the PR. Otherwise mark "vetted".

Begin looping through all PRs in the reverse order of the state machine (closest to merge first).

If a PR has progressed to copilot-review, and there are copilot review comments that haven't been addressed, copy those comments into a new review comments for Jules (as Jules cannot see Copilot review comments). Set state to "changes-requested". Also, if GH Workflows are failing, post comment requesting fixes and set to changes-requested. Otherwise, present the user with a summary of the PR following the same format as the unvetted summary, including enough information for the User to make a final determination to merge the PR. Follow User's command (merge / request changes / close).

If a PR is in changes-requested and Jules has responded, perform a brief review to determine if the PR is ready for copilot-review. If so, move to copilot-review and (re-)request review from Copilot. If not, post comment requesting additional changes. Also check GH Workflows and request fixes if necessary.

If a PR is in "changes-requested" or "copilot-review" and it has been 30 minutes since the last request for changes/review, mark it as "agent-stalled". The user will need to determine the next course of action.

If the PR has merge conflicts, mark it as "merge-conflicts". The user will need to guide the conflict resolution.

The user must approve all actions, including adding/changing labels, posting review comments and most especially, vetting and merging.

Attempt to investigate all open PRs in one turn. Keep a log of each open PR, it's state and notes on it's state. Each iteration of the skill will have it's own log entry, encompassing all PRs. Collect trivial decisions (change label, request Workflow fixes or repost Copilot comments) and note them in your log. Present the merge decisions, first, one PR at a time. Vetting decisions after. Then present trivial decisions and present to the user together in a numbered list, allowing the user to approve all or only some. Note each decision in your log and batch process all decisions after all PRs have been decided.