New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Publish Changes

by Porabuild in Porabuild/Poracode

Commit work, push a branch, and open a pull request with an accurate description.

Apache-2.0Auto-check passedDevelopment

Install Publish Changes

skills CLI
$ npx skills add Porabuild/Poracode --skill publish-changes -a claude-code

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

GitHub CLI
$ gh skill install Porabuild/Poracode publish-changes --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/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/github/skills/publish-changes .claude/skills/publish-changes && 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
publish-changes
GitHub stars
114
Token cost
~423 tokens
SKILL.md length
264 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Commit work, push a branch, and open a pull request with an accurate description.

  • Tasks that involve Pull requests
  • SKILL.md covers Before committing, The commit, The pull request and After
  • Calls git

What it does

Publish Changes is an agent skill from Porabuild/Poracode. Commit work, push a branch, and open a pull request with an accurate description.

Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/publish-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit bffd89d. 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

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Publish Changes loads about 423 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 264 words of instructions outside code blocks.

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

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 Porabuild/Poracode at commit bffd89d, republished under its Apache-2.0 licence (© Porabuild). 264 words, ~423 tokens.

Download SKILL.mdSave it as .claude/skills/publish-changes/SKILL.md (or your agent's skills folder).
name
publish-changes
description
Commit work, push a branch, and open a pull request with an accurate description.

Publish Changes

Get finished work onto a branch and into a pull request.

Before committing

Committing and pushing are the user's call. Do them when asked, not because the work looks done.

Check the current branch first. If it is the default branch, create a new one instead of committing to it.

Review what is actually staged. Never git add -A over a tree you have not looked at — stray artifacts, local config, and secrets get committed that way. Stage the files you changed on purpose.

The commit

Write a message that says what changed and why, in the style already used in the repository's history. Match its existing conventions rather than importing your own.

Do not skip hooks or bypass signing. If a hook fails, fix what it caught.

The pull request

The description should let a reviewer understand the change without reading every line of the diff: what it does, why, and anything that needs a decision. Note what you did not do — deliberate omissions, follow-ups, known gaps.

Do not describe tests as passing unless you ran them and saw them pass. If something is unverified, say which part and why.

When the user asked you to publish the finished work, that authorizes the commit, push, and draft PR described by this workflow. Ask only when the branch, included changes, target repository/base, or PR content is materially ambiguous. Read the created PR back after opening it and verify its head, base, title, and URL.

After

Report the branch name and the PR URL. If CI starts and fails, ci-debug covers the diagnosis.

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

Files

Just SKILL.md in resources/plugins/github/skills/publish-changes of Porabuild/Poracode.

Open the folder on GitHubat commit bffd89d

Compare with similar skills

Publish Changes 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.

Publish Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Publish Changes this skillPorabuild/Poracode114—~423Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    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

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from Porabuild/Poracode

All 21 skills in this repo

  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    114 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    114 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    114 GitHub stars~745 tokensUpdated today
    Auto-check passed

  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    114 GitHub stars~691 tokensUpdated today
    Auto-check passed

  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    114 GitHub stars~718 tokensUpdated today
    Auto-check passed

Categories

Questions about Publish Changes

What does Publish Changes do?

Commit work, push a branch, and open a pull request with an accurate description. Publish Changes is an agent skill from Porabuild/Poracode. Commit work, push a branch, and open a pull request with an accurate description.

When should I use Publish Changes?

Publish Changes fits situations like: tasks that involve Pull requests.

How do I install Publish Changes in Claude Code?

Run `npx skills add Porabuild/Poracode --skill publish-changes -a claude-code`. Or copy the skill folder (resources/plugins/github/skills/publish-changes in Porabuild/Poracode) into .claude/skills/publish-changes in your project. Claude Code loads it when a task matches its description.

How do I install Publish Changes in Codex?

Run `npx skills add Porabuild/Poracode --skill publish-changes -a codex`. Or copy the skill folder (resources/plugins/github/skills/publish-changes in Porabuild/Poracode) into .agents/skills/publish-changes in your project. Codex loads it when a task matches its description.

Can I use Publish Changes 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 Porabuild/Poracode --skill publish-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-changes, .gemini/skills/publish-changes, .github/skills/publish-changes and .opencode/skills/publish-changes in your project.

What does Publish Changes need to run?

Going by SKILL.md and its folder, Publish Changes needs the command-line tools its instructions call (git).

Does Publish Changes access the network?

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

Is Publish Changes 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 Publish Changes use?

Publish Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Publish Changes use?

About 423 tokens (SKILL.md is roughly 1.7k 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 Publish Changes?

Skills that share tags, products or a category with Publish Changes: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Publish Changes?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

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