New: 98,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

Voyager Contribute

by voyager-crew in voyager-crew/voyager

Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

GPL-3.0Auto-check passedDevelopment

Install Voyager Contribute

skills CLI
$ npx skills add voyager-crew/voyager --skill voyager-contribute -a claude-code

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

GitHub CLI
$ gh skill install voyager-crew/voyager voyager-contribute --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/voyager-crew/voyager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/voyager-contribute .claude/skills/voyager-contribute && 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
voyager-contribute
GitHub stars
20k
Token cost
~1.2k tokens
SKILL.md length
697 words
Files
4 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
GPL-3.0

At a glance

Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

  • Works in 3 steps: Preflight → Verify → Commit and publish
  • Tasks that involve Pull requests
  • SKILL.md covers 1. Preflight, 2. Verify and 3. Commit and publish
  • Calls git, bun and gh

What it does

Voyager Contribute is an agent skill from voyager-crew/voyager. Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/browser-testing.md` and `references/repo-traps.md`).

It sits in Development, covering Pull requests. It works with Chrome Extensions and GitHub. The repository describes itself as: Enhancement suite for Gemini, AI Studio, Claude, ChatGPT & DeepSeek — plus a prompt manager for any website, DeepSeek Harness included. / 面向 Gemini、AI Studio、Claude、ChatGPT 与… The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/voyager-contribute”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Preflight
  2. Verify
  3. Commit and publish

What it can do on your machine

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

Voyager Contribute loads about 1.2k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 697 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.9k

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 voyager-crew/voyager at commit e854e34, republished under its GPL-3.0 licence (© voyager-crew). 697 words, ~1,229 tokens.

Download SKILL.mdSave it as .claude/skills/voyager-contribute/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
voyager-contribute
description
Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

Voyager Contribution

Use only the stages included in the user's request; a readiness review delivers findings, while an authorized commit or publication continues through verification and handoff. Route issue investigation to issue-review, Safari loading or native verification to update-safari-extension, and releases to release when needed.

1. Preflight

  1. Inspect git status --short --branch, the current branch, and the diff. Preserve unrelated work.
  2. Read the linked Issue and its comments when one exists. A new feature needs explicit maintainer approval of the approach, either in the Issue or as a direct instruction in the current task; assignment or /claim only selects an owner.
  3. Work on one focused topic branch targeting main. Keep secrets and generated dist_* artifacts out of commits.
  4. Read repo-traps.md — the repository-specific pitfalls that have cost past contributors the most review rounds.
  5. Use gh as the source of truth for Issue/PR state. Before any GitHub write, confirm gh auth status shows the account you intend to contribute as. If GitHub CLI is unavailable, perform Issue/PR reads and writes through the GitHub web UI instead and note that in the PR.

Preflight is complete when the Issue or rationale, approval state, intended scope, current branch, and clean ownership of every changed file are known.

2. Verify

  1. Add or update regression tests for behavior changes. If no useful automated test exists, record the reason.

  2. Use the verification matrix in AGENTS.md: code PRs require bun run verify:pr; prose-only changes use the applicable document checks. During implementation, run focused checks; reuse passing evidence for unchanged inputs. If formatting or lint fixes are needed, apply them to the intended files with bun run format <paths> / bun run lint <paths> and inspect the diff before checking the final tree. Read-only reviews use check variants.

    verify:pr covers local automation and production browser builds; it does not prove that an extension loaded or that live behavior works. Finish with git diff --check and git status --short.

  3. For runtime, UI, manifest, permission, packaging, native, or plugin changes, read browser-testing.md and collect the required live evidence.

  4. Record every omitted command or browser check with its reason. For required coverage that another person must complete, name the browser and owner and leave the item pending.

Verification is complete when every applicable automated check and browser check has a truthful result, the working tree matches the snapshot being tested, and remaining work is explicitly assigned.

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

3. Commit and publish

  1. Review the final diff and stage only intended paths.

  2. Create a Conventional Commit with a lowercase scope and a header no longer than 100 characters. Add Fixes #<issue> or Closes #<issue> when appropriate. Retain the active agent's project-standard co-author footer; Codex-authored commits use:

    text
    Co-authored-by: Codex <codex@users.noreply.github.com>

  3. Inspect the commit with git show --stat --format=fuller HEAD and git status --short. Require no staged or unstaged changes in the contribution's paths; preserve and disclose unrelated pre-existing work. HEAD is the tested commit only while the verified paths match it, and any later change invalidates affected evidence.

  4. When publishing is authorized, push only the topic branch and open or update a draft PR targeting main. Contributors never push directly to main; use force-push only with explicit user approval — this repository squash-merges, so a merged branch will later look unmerged (see repo-traps.md) and must be deleted, not re-pushed. Exception: this rule governs contribution workflows; a maintainer with push access working outside a contribution follows the project-wide default push rules in CLAUDE.md/AGENTS.md, which take precedence.

  5. In the PR, state the linked Issue or direct authorization/rationale, scope, tested commit, commands run, live browser evidence, screenshots for UI changes, and all pending checks. Re-run affected checks after review changes.

  6. Verify the PR author, base branch, commit set, changed files, and CI state with gh before handoff.

Publishing is complete when the focused diff is on a topic branch, the draft PR accurately reports its evidence and gaps, and the user receives the PR URL plus pending review or CI work.

After an Issue fix lands, leave a short comment in the reporter's language: the fix has landed, it will be available in the next version, and the Issue may be reopened if the problem remains.

© voyager-crew, GPL-3.0. 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 3 other files (references) in .agents/skills/voyager-contribute of voyager-crew/voyager.

  • SKILL.md
  • agents/openai.yaml
  • references/browser-testing.md
  • references/repo-traps.md

Open the folder on GitHubat commit e854e34

Compare with similar skills

Voyager Contribute 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.

Voyager Contribute compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Voyager Contribute this skillvoyager-crew/voyager20k—~1.2kAutomated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • 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

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from voyager-crew/voyager

  • Create Voyager Plugin

    voyager-crew/voyager

    Create or change a Voyager declarative plugin, site adapter, or native primitive.

    20k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Release

    voyager-crew/voyager

    Prepare, publish, or recover a Voyager release. An agent skill from voyager-crew/voyager.

    20k GitHub stars~814 tokensUpdated today
    Auto-check passed

  • Update Safari Extension

    voyager-crew/voyager

    Build, reload, and verify Voyager in Safari for web-extension changes, native integration, or signed-app testing while preserving installed apps and extension data.

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

  • Verify In Browser

    voyager-crew/voyager

    Verify Voyager content-script or injected-CSS behavior in a live browser, including stale-build diagnosis.

    20k GitHub stars~886 tokensUpdated today
    Auto-check passed

  • Issue Review

    voyager-crew/voyager

    Investigate or fix a referenced Voyager GitHub issue, within the requested delivery scope.

    20k GitHub stars~289 tokensUpdated today
    Auto-check passed

  • PR Description

    voyager-crew/voyager

    Write or rewrite a Voyager pull request description. An agent skill from voyager-crew/voyager.

    20k GitHub stars~182 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Voyager Contribute

What does Voyager Contribute do?

Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness. Voyager Contribute is an agent skill from voyager-crew/voyager. Prepare Voyager commits, pull requests, and contribution evidence, or claim an issue and check review readiness.

When should I use Voyager Contribute?

Voyager Contribute fits situations like: tasks that involve Pull requests.

How do I install Voyager Contribute in Claude Code?

Run `npx skills add voyager-crew/voyager --skill voyager-contribute -a claude-code`. Or copy the skill folder (.agents/skills/voyager-contribute in voyager-crew/voyager) into .claude/skills/voyager-contribute in your project. Claude Code loads it when a task matches its description.

How do I install Voyager Contribute in Codex?

Run `npx skills add voyager-crew/voyager --skill voyager-contribute -a codex`. Or copy the skill folder (.agents/skills/voyager-contribute in voyager-crew/voyager) into .agents/skills/voyager-contribute in your project. Codex loads it when a task matches its description.

Can I use Voyager Contribute 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 voyager-crew/voyager --skill voyager-contribute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/voyager-contribute, .gemini/skills/voyager-contribute, .github/skills/voyager-contribute and .opencode/skills/voyager-contribute in your project.

What does Voyager Contribute need to run?

Going by SKILL.md and its folder, Voyager Contribute needs the command-line tools its instructions call (git, bun and gh).

Does Voyager Contribute 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 Voyager Contribute 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 Voyager Contribute use?

Voyager Contribute is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Voyager Contribute use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Voyager Contribute?

Skills that share tags, products or a category with Voyager Contribute: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Voyager Contribute?

voyager-crew (a GitHub organization) maintains it in voyager-crew/voyager, which has 20,349 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.

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