Agent skill

Workflow PR Sync

by macalbert in macalbert/envilder

Create or update a GitHub pull request with an auto-generated title and description from branch commits.

MITAuto-check passedDevelopment

Install Workflow PR Sync

skills CLI
$ npx skills add macalbert/envilder --skill workflow-pr-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install macalbert/envilder workflow-pr-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/workflow-pr-sync .claude/skills/workflow-pr-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-pr-sync
GitHub stars
138
Token cost
~828 tokens
SKILL.md length
433 words
Files
2
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Create or update a GitHub pull request with an auto-generated title and description from branch commits.

  • Works in 7 steps: Get the current branch: git branch… → Determine the base branch from the… → Check if a PR already exists → …
  • Syncing PR description
  • SKILL.md covers When to Use, Procedure, PR Title and Constraints, plus 1 more section
  • Calls git and gh

What it does

Workflow PR Sync is an agent skill from macalbert/envilder. Create or update a GitHub pull request with an auto-generated title and description from branch commits. Use when opening a PR, syncing PR description, or preparing a branch for review.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Development, covering Pull requests. It works with GitHub and PowerShell. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

  • Syncing PR description
  • Preparing a branch for review

Example prompts

  • “/workflow-pr-sync”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Get the current branch: git branch --show-current
  2. Determine the base branch from the optional argument; if none is
  3. Check if a PR already exists
  4. Get the final diff against base to understand what the PR actually
  5. Optionally get commits for context: git log ..HEAD --oneline
  6. Generate PR title and body following the template.
  7. Create or update the PR using --body-file (see constraints).

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow PR Sync loads about 828 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~828

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 433 words, ~828 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-pr-sync/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
workflow-pr-sync
description
Create or update a GitHub pull request with an auto-generated title and description from branch commits. Use when opening a PR, syncing PR description, or preparing a branch for review.
argument-hint
optional base branch (default: main)

PR Sync

Create or update a GitHub pull request for the current branch.

When to Use

  • Opening a new pull request
  • Updating an existing PR title or description after new commits
  • Preparing a branch for code review

Procedure

  1. Get the current branch: git branch --show-current
  2. Determine the base branch from the optional argument; if none is provided, default to main.
  3. Check if a PR already exists:
    • PowerShell: gh pr view --json number,title,url 2>$null
    • Bash/Zsh: gh pr view --json number,title,url 2>/dev/null
  4. Get the final diff against base to understand what the PR actually changes: git diff <base>...HEAD --stat (three-dot merge-base diff). Use this: not the commit list: as the source of truth for the PR body. Commits may include merge commits or changes already in main.
  5. Optionally get commits for context: git log <base>..HEAD --oneline
  6. Generate PR title and body following the template. The template is mandatory: all four sections (Summary, Changes, Testing, Related) must appear in every PR body, exactly in that order. The body must describe the final diff vs base, not individual commits.
  7. Create or update the PR using --body-file (see constraints).

PR Title

Use the conventional commit format of the most significant commit:

txt
<type>(<scope>): <description>

If the branch has a single commit, use that commit's message as the title.

Show full SKILL.md (216 more words)Show less

Constraints

  • Never force-push or amend published commits
  • Always target main unless the user specifies otherwise
  • Always use --body-file with a temp file: never pass markdown inline via --body (PowerShell corrupts backticks in inline strings)
  • Never use the VS Code PR creation tool: always use gh CLI with --body-file to ensure template compliance and avoid encoding issues
  • All four template sections are mandatory: do not skip, reorder, or replace with freeform text
  • If gh CLI is not available, output the title and body for manual creation
  • Never use PowerShell here-strings (@"..."@) to generate the PR body: use create_file to write the .pr-body.md file directly instead. Here-strings corrupt backticks (` becomes escape char, e.g. `0 = NUL), arrows (→), em-dashes (—), and other non-ASCII characters.
  • Avoid non-ASCII characters in PR bodies: use plain ASCII alternatives: to instead of →, -- instead of —, etc.
  • Never hard-wrap prose at a fixed column width: write each Summary sentence and each Changes bullet as a single unbroken line, no matter how long. GitHub renders a single \n inside a paragraph or list item as a visible line break, so hard-wrapped text (e.g. wrapped at ~80 chars) shows up as broken, choppy lines instead of flowing text. Only insert a real newline between sections or between separate bullets.

Commands

See reference.md for the PR body template and gh CLI commands.

© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .github/skills/workflow-pr-sync of macalbert/envilder.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Workflow PR Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow PR Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow PR Sync this skillmacalbert/envilder138—~828Automated safety check: PassMIT
Find Regression Riskdotnet/maui23k—~1.1kAutomated safety check: PassMIT
Find Reviewable MAUI PRsdotnet/maui23k—~1.7kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Ansible Backport Creatoransible/ansible71k—~1.2kAutomated safety check: PassGPL-3.0
CI Act Runchewiebug/GCViewer4.6k—~2.4kAutomated safety check: NotesCustom licence

Similar skills

  • Official

    Checks a pull request for lines that undo a recent bug fix by comparing what the PR removes with what labeled bug-fix PRs added to the same files.

    23k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Lists open pull requests in dotnet/maui and dotnet/docs-maui that are worth reviewing next, ranked by priority labels, milestone and partner or community origin.

    23k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed
  • CI Act Run

    chewiebug/GCViewer

    Run the full build-and-deploy.yaml workflow locally via act + Docker.

    4.6k GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check: notes
  • Qiaomu Meta Skill

    joeseesun/qiaomu-meta-skill

    Research, create, improve, migrate, evaluate, package, install-check, govern, and safely publish qiaomu-flavored agent skills from workflows, prompts, transcripts, docs, SOPs, runbooks, scripts, or…

    383 GitHub stars~2.8k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from macalbert/envilder

All 30 skills in this repo
  • Code Review Perspectives

    macalbert/envilder

    Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

    138 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed
  • Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • Common Git

    macalbert/envilder

    Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

    138 GitHub stars~991 tokensUpdated 2 days ago
    Auto-check passed
  • Common Testing Conventions

    macalbert/envilder

    Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).

    138 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Doc Maintenance

    macalbert/envilder

    Workflow for maintaining changelogs, READMEs, and documentation files.

    138 GitHub stars~904 tokensUpdated 2 days ago
    Auto-check passed
  • Doc Sync

    macalbert/envilder

    Audit and synchronize documentation across website, READMEs, and docs/.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

Questions about Workflow PR Sync

What does Workflow PR Sync do?

Create or update a GitHub pull request with an auto-generated title and description from branch commits. Workflow PR Sync is an agent skill from macalbert/envilder. Create or update a GitHub pull request with an auto-generated title and description from branch commits.

When should I use Workflow PR Sync?

Workflow PR Sync fits situations like: syncing PR description; preparing a branch for review.

How do I install Workflow PR Sync in Claude Code?

Run `npx skills add macalbert/envilder --skill workflow-pr-sync -a claude-code`. Or copy the skill folder (.github/skills/workflow-pr-sync in macalbert/envilder) into .claude/skills/workflow-pr-sync in your project. Claude Code loads it when a task matches its description.

How do I install Workflow PR Sync in Codex?

Run `npx skills add macalbert/envilder --skill workflow-pr-sync -a codex`. Or copy the skill folder (.github/skills/workflow-pr-sync in macalbert/envilder) into .agents/skills/workflow-pr-sync in your project. Codex loads it when a task matches its description.

Can I use Workflow PR Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill workflow-pr-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-pr-sync, .gemini/skills/workflow-pr-sync, .github/skills/workflow-pr-sync and .opencode/skills/workflow-pr-sync in your project.

What does Workflow PR Sync need to run?

Going by SKILL.md and its folder, Workflow PR Sync needs the command-line tools its instructions call (git and gh).

Does Workflow PR Sync access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Workflow PR Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workflow PR Sync use?

Workflow PR Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow PR Sync use?

About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow PR Sync?

Skills that share tags, products or a category with Workflow PR Sync: Find Regression Risk (dotnet/maui, 23k stars), Find Reviewable MAUI PRs (dotnet/maui, 23k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Ansible Backport Creator (ansible/ansible, 71k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow PR Sync?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.