Skip to content

t1082: Skill update PR pipeline — skill-update-helper.sh pr command#1593

Merged
marcusquinn merged 3 commits intomainfrom
feature/t1082
Feb 18, 2026
Merged

t1082: Skill update PR pipeline — skill-update-helper.sh pr command#1593
marcusquinn merged 3 commits intomainfrom
feature/t1082

Conversation

@marcusquinn
Copy link
Owner

Summary

New pr subcommand for skill-update-helper.sh that creates worktree + PR per skill with upstream changes. Designed for repo maintainers to review/merge skill updates into the shared repo.

Pipeline flow

  1. Check all skills in skill-sources.json for upstream commit changes
  2. For each skill with updates:
    • Skip if PR already exists for that skill
    • Create worktree (chore/skill-update-<name> branch)
    • Re-import skill via add-skill-helper.sh add --force
    • Commit with upstream metadata
    • Push and create PR via gh pr create
  3. Report summary (created/skipped/failed)

Features

  • --dry-run to preview what PRs would be created
  • Single skill targeting: skill-update-helper.sh pr cloudflare
  • Duplicate PR detection (skips if open PR exists for branch)
  • Worktree cleanup on failure (removes empty worktrees)
  • Uses worktree-helper.sh when available, falls back to direct git
  • Registers worktree ownership for cross-session safety

Usage

# Create PRs for all skills with updates
skill-update-helper.sh pr

# Create PR for a specific skill
skill-update-helper.sh pr cloudflare

# Preview what PRs would be created
skill-update-helper.sh pr --dry-run

Ref #1586

New `pr` subcommand creates worktree + PR per skill with upstream changes.
Pipeline: check upstream commits -> create worktree per skill -> re-import
via add-skill-helper.sh -> commit -> push -> gh pr create.

Supports --dry-run, single skill targeting, and duplicate PR detection.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 17, 2026

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 0 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/t1082

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 16 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 17 23:55:39 UTC 2026: Code review monitoring started
Tue Feb 17 23:55:40 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 16

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 16
  • VULNERABILITIES: 0

Generated on: Tue Feb 17 23:55:42 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

ClawdHub and other non-GitHub skill sources now show an informational
skip message instead of a confusing URL parse warning.
@marcusquinn marcusquinn marked this pull request as ready for review February 17, 2026 23:56
@gemini-code-assist
Copy link

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the skill-update-helper.sh script by introducing a new pr subcommand. This command automates the entire process of bringing upstream skill changes into the main repository, from identifying updates to creating ready-to-review pull requests. It aims to streamline the maintenance workflow by reducing manual steps and ensuring consistency in skill updates.

Highlights

  • New pr subcommand: Introduced a new pr subcommand to skill-update-helper.sh that automates the creation of pull requests for skills with upstream updates.
  • Automated PR Workflow: The new command creates a dedicated Git worktree for each updated skill, re-imports the skill, commits the changes with upstream metadata, pushes the branch, and then creates a pull request using the gh CLI.
  • Maintainer-focused Design: This feature is designed to assist repository maintainers in reviewing and merging skill updates into the main repository efficiently.
  • Key Features: Includes --dry-run for previewing PRs, targeting specific skills, detection of existing open PRs to prevent duplicates, automatic worktree cleanup on failure, and robust worktree management using worktree-helper.sh or direct Git commands.
Changelog
  • .agents/scripts/skill-update-helper.sh
    • Added pr command to the script's usage instructions and help output.
    • Introduced a new --dry-run option for previewing PR creation without making actual changes.
    • Implemented cmd_pr function to orchestrate the PR creation pipeline, including checking for updates, managing worktrees, committing changes, and pushing branches.
    • Developed cmd_pr_single function to handle the creation of a single skill update PR, encompassing worktree creation, skill re-import, commit message generation, and GitHub PR creation via gh CLI.
    • Added helper functions get_repo_root and get_default_branch for Git repository context.
    • Included _cleanup_worktree function to remove empty worktrees and associated branches upon failure.
    • Integrated the new pr command into the main argument parsing logic of the script.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 16 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 17 23:56:46 UTC 2026: Code review monitoring started
Tue Feb 17 23:56:46 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 16

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 16
  • VULNERABILITIES: 0

Generated on: Tue Feb 17 23:56:48 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a powerful pr command to skill-update-helper.sh, automating the creation of pull requests for skill updates. The implementation is comprehensive, including features like --dry-run, worktree management, and duplicate PR detection. The code is well-structured and includes error handling. My review includes a few suggestions to improve maintainability, robustness, and adherence to the project's style guide.

- Capture stderr from git commit/push/worktree-add/gh-pr-create instead
  of suppressing with 2>/dev/null (high priority review feedback)
- Simplify redundant GitHub URL check condition (medium)
@github-actions
Copy link

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 16 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Wed Feb 18 00:04:16 UTC 2026: Code review monitoring started
Wed Feb 18 00:04:16 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 16

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 16
  • VULNERABILITIES: 0

Generated on: Wed Feb 18 00:04:19 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@sonarqubecloud
Copy link

@marcusquinn marcusquinn merged commit 1f36c94 into main Feb 18, 2026
18 of 19 checks passed
@marcusquinn marcusquinn deleted the feature/t1082 branch February 18, 2026 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant