skills.rest
outfitter-dev
outfitter-devOFFICIAL
Explore all skills by this author →
Website𝕏@outfitter_devGitHub

agent-browser-upstream

Sync agent-browser fork with upstream and generate integration documentation.

2|Updated Jan 14, 2026
Search Tags:#documentation#integration#sync#fork#navigator#agent-browser
One-click install
npx skills add https://github.com/outfitter-dev/navigator --skill agent-browser-upstream
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-browser-upstream
Source: https://github.com/outfitter-dev/navigator/tree/main/.claude/skills/agent-browser-upstream
Command: npx skills add https://github.com/outfitter-dev/navigator --skill agent-browser-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve?

Navigator teams need a reliable, auditable workflow to keep the agent-browser fork in sync with upstream, continuously analyze changes, and generate integration planning documentation.

Core Features & Use Cases

  • Automated fork synchronization: clones and configures remotes automatically if missing, fetches updates from origin and upstream, and prepares integration artifacts.
  • Change analysis & risk visibility: classifies commits into breaking, additive, and fixes, and highlights critical file changes that may impact Navigator.
  • Documentation & planning: produces versioned integration notes, release-artifacts, and an issue-ready integration plan to track work.

Quick Start

Run the upstream sync workflow to align navigator's agent-browser fork with upstream and generate integration planning docs.

Frequently Asked Questions about agent-browser-upstream

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

FAQPage Schema
How do I sync a forked agent-browser repository with the upstream vercel-labs version?▼

To sync a forked agent-browser repository, the workflow automates cloning, configures Git remotes, fetches updates from both origin and upstream, and generates versioned integration planning documentation.

How does automated fork synchronization classify upstream commits for risk analysis?▼

Automated fork synchronization classifies upstream commits into breaking changes, additive updates, and fixes, highlighting critical file modifications that may impact your navigator integration.

Do I need bun and Git installed to run the agent-browser upstream sync workflow?▼

Yes, you need bun and Git installed, along with access to both the navigator agent-browser fork and the upstream vercel-labs repository, to perform the sync and documentation generation steps.

What is the best way to generate integration documentation after syncing a fork?▼

The best way to generate integration documentation is running the automated sync workflow, which produces versioned integration notes, release artifacts, and an issue-ready integration plan to track maintenance work.

What should I do if my agent-browser fork is missing the upstream remote configuration?▼

If your agent-browser fork is missing the upstream remote configuration, the sync workflow automatically clones the repository if missing and configures the necessary Git remotes before fetching updates.

Can I use this workflow to track breaking changes before integrating upstream agent-browser updates?▼

Yes, you can use this workflow to track breaking changes, as it analyzes upstream commits, classifies them by impact level, and highlights critical file changes that may affect your navigator integration.

Related Skills

Explore More Software Engineering Skills→
enunoenuno

fork-fleet

Monitor code and configuration divergence between fleet forks and upstream repositories.

Community
Advanced
webrix-aiwebrix-ai
1

release-notes

Generate release notes from merged pull requests, commits, and resolved issues.

Official
Intermediate
peterfeipeterfei
420

changelog-generator

Generate CHANGELOG.md from Git commit history using Conventional Commits.

Community
Intermediate
shysssthanhtrishysssthanhtri

gitnexus-impact-analysis

Analyze code changes to identify breakage risks with dependency queries and git-diff mapping.

Community
Intermediate