Skip to content
cccskills
FreePublished on GitHub

open-pr

Prepare repository changes for review by creating a named branch, committing with a Conventional Commit message, pushing it, and opening a GitHub pull request. The workflow also covers adding required attribution and returning the PR link.

OriginalShow the original description

Create a branch, commit, push, and open a GitHub pull request from the sandbox. Use when a user asks to modify a repository, commit changes, push a branch, or open or update a PR.

paradigmxyz/centaur1,405 stars(GitHub 1,405 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Good for

  • Opening a pull request for repository changes
  • Pushing an authorized branch to GitHub
  • Updating an existing pull request

Files included (1)

  • SKILL.md1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Open a PR

Repos under ~/github/ are read-only. Never commit or push there.

Workflow

  1. Choose a short, lowercase, kebab-case slug that describes the change. Never omit it or use a numeric fallback.
  2. Create a writable clone:
git-branch <org/repo> <branch-slug>
# e.g. git-branch paradigmxyz/centaur fix-auth-token-refresh

The clone lives at ~/branches/<org>/<repo> on centaur/<branch-slug>-<timestamp>. 3. Make the change there and run the repo's checks for the changed surfaces. 4. Commit with a Conventional Commit message, push, and open the PR with gh pr create. Use a Conventional Commit title. 5. Add the Prompted by: ... attribution line required by the system prompt to the PR body. 6. Reply with the PR link.

Push work in progress only when the user authorized remote git work. For an authorized PR, push before finishing so container recycling cannot lose the work.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Investigate authentication, permission, credential, OAuth, token, secret, and API proxy failures by checking live VictoriaLogs evidence first. Summarize relevant status codes and error details, and distinguish upstream denials from local proxy or secret resolution problems.

  • Investigate a 401, 403, or 503 response
  • Trace an integration authentication failure
  • Check why a credential or secret is not resolving
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

centaur

FreeSummary

Use an authenticated Centaur MCP deployment to find and call team-approved tools. It checks identity when permissions matter, follows the deployment’s current CLI help, and summarizes consequential changes with relevant identifiers or links.

  • Finding the right approved Centaur tool
  • Running an unfamiliar Centaur CLI command
  • Checking the signed-in user's permissions
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

Use this skill to translate a Console administrator’s request into Centaur permission changes. It can create supported principals and secrets, grant or revoke access, adjust Slack and sandbox permissions, and manage Slack Connect allowlists while checking for unsafe personal credential sharing.

  • Grant a Slack channel access to a shared tool credential
  • Create a principal for a Slack channel, user, or workflow
  • Adjust a channel’s access to another Slack channel
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

Investigate Centaur incidents using VictoriaLogs for runtime logs and VictoriaMetrics for deployment and health metrics. The skill correlates a narrow time window with relevant code and workflow status, then reports a supported cause or bounded hypotheses and the evidence still needed.

  • Investigating a stalled workflow or missing post
  • Checking thread and execution evidence
  • Reviewing tool-call or sandbox activity
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

company-context

FreeSummary

Answer internal history and project context questions by searching indexed company information and checking relevant live sources such as Slack, Linear, Google Docs, Drive, Calendar, or Granola. Reconcile the evidence and cite dates or source links when available.

  • Find what was discussed or decided internally
  • Check a project's prior context or current status
  • Search meeting notes and calendar events
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

creating-tools

FreeSummary

Build a new external service integration as a packaged Python CLI. The skill guides the project layout, API client, command-line interface, credential declarations, health check, and tests so the tool can be installed and used by agents.

  • Create a tool for a new external API
  • Build a Python client for a service
  • Add a CLI command for an integration
paradigmxyz/centaur1.4KUpdated Oct 26, 2026

See all skills by paradigmxyz

Report a problem with this skill