skills.rest
Nagi-ovo
Nagi-ovoCOMMUNITY
Explore all skills by this author →
Website𝕏@Nag1ovoGitHub

voyager-contribute

Guides Voyager contributions through issue review, verification, commit, and pull request workflows.

19.9k|659|Updated Oct 4, 2025
Search Tags:#contribution#regression testing#Conventional Commits#browser extension#GitHub workflow#Code review#Pull request
One-click install
npx skills add https://github.com/Nagi-ovo/gemini-voyager --skill voyager-contribute
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: voyager-contribute
Source: https://github.com/Nagi-ovo/gemini-voyager/tree/main/.agents/skills/voyager-contribute
Command: npx skills add https://github.com/Nagi-ovo/gemini-voyager --skill voyager-contribute

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Contributing to the Voyager browser extension requires coordinating issue approval, regression testing, multi-browser verification, conventional commits, and draft PRs, and missing any step costs review rounds. This Skill enforces the complete contribution workflow so changes arrive review-ready with truthful evidence.

Core Features & Use Cases

  • Structured Preflight: Inspects git state, confirms issue approval and scope, reads regression notes and repository-specific traps before any code change.
  • Verification Gates: Runs formatting, linting, and the verify:pr suite, then routes runtime or UI changes to browser testing references for Loaded and Live evidence on Chrome, Firefox, Edge, and Safari.
  • Compliant Publishing: Produces Conventional Commits with co-author footers, pushes only topic branches, and opens draft PRs documenting tested commits, commands, and pending checks.
  • Use Case: A contributor fixing a Gemini export bug uses this Skill to confirm issue approval, run the PR suite, collect live browser evidence, commit with a proper scope, and open a draft PR that passes review on the first round.

Quick Start

Use the voyager-contribute skill to prepare and publish my current Voyager changes as a draft pull request with full verification evidence.

Frequently Asked Questions about voyager-contribute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I contribute a pull request to the Voyager browser extension?▼

Work on a focused topic branch targeting main after confirming issue approval, run bun run format, lint, and verify:pr, then commit with a Conventional Commit and open a draft PR. The PR must state the tested commit, commands run, and browser evidence.

What browser testing is required before a Voyager PR is review-ready?▼

Runtime, UI, manifest, or packaging changes require Loaded and Live evidence on Chrome and Firefox, with Edge added for Chromium-specific behavior and Safari when affected. Docs or test-only changes only need automated checks with an explanation.

Why does my merged Voyager branch show as unmerged after the PR closes?▼

The repository squash-merges pull requests, so the local branch no longer matches main after merging. Delete the branch and create a fresh one from main instead of re-opening a PR from the old branch.

Can I push directly to main or force-push a Voyager contribution branch?▼

Contributors never push directly to main; only topic branches are pushed. Force-push requires explicit user approval, and the PR title must follow the type(scope): summary format since it becomes the squash commit header.

How do I add support for a new site like ChatGPT or Claude to Voyager?▼

New site support goes through the plugin system: declarative CSS and JSON plugins go in the bundled catalog, while native-function plugins go in builtin with default-disabled state and start/stop lifecycle. Never add static content_scripts or required host_permissions to manifests without prior issue approval.

Related Skills

Explore More Software Engineering Skills→
gittowergittower
413

create-spec

Convert accepted reports into implementation-ready GitHub spec issues.

Official
Advanced
airhornsairhorns

land

Monitor GitHub PR conflicts and CI checks, then squash-merge when green.

Community
Advanced
thingpersonthingperson

cross-browser

Generate a cross-browser testing checklist from recent code changes.

Community
Intermediate
ievo-aiievo-ai

inspect

Summarize remote GitHub skill repositories via the gh CLI.

Official
Intermediate