fork-manager
Manage forks with open PRs - sync upstream, rebase branches, track PR status, and maintain production branches with pending contributions. Supports automatic conflict resolution via --auto-resolve flag (spawns AI subagents to resolve rebase conflicts). Use when syncing forks, rebasing PR branches, building production branches that combine all open PRs, reviewing closed/rejected PRs, or managing local patches kept outside upstream. Requires Git and GitHub CLI (gh).
Why use this skill?
Automate fork synchronization, PR rebasing, and local patch management. Maintain complex Git repositories with AI-driven conflict resolution.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/glucksberg/fork-managerWhat This Skill Does
The fork-manager skill is an advanced agentic utility designed to streamline the maintenance of complex Git repositories where multiple forks, pending pull requests, and local patches converge. Unlike basic Git commands, this skill acts as an intelligent orchestrator that manages the entire lifecycle of a development fork. It automatically tracks the status of open PRs, performs rebasing operations to keep your local branches current with upstream changes, and can construct a cohesive 'production branch' that integrates all your open contributions alongside locally managed patches that haven't been upstreamed.
Installation
To integrate this skill into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/glucksberg/fork-manager
Ensure you have the GitHub CLI (gh) authenticated and Git configured locally, as these are mandatory dependencies for the skill's operation.
Use Cases
- Continuous Synchronization: Keep your fork perfectly aligned with upstream repository developments without manual intervention.
- PR Maintenance: Automated rebasing of feature branches onto the latest upstream commit, including conflict resolution via AI-driven subagents.
- Unified Build Management: Generate a deployment branch that aggregates all open PRs plus custom patches into a single, functional codebase.
- Patch Lifecycle Tracking: Analyze closed or rejected PRs to determine if the logic should be preserved as local patches or archived.
Example Prompts
- "Sync my main fork with the upstream origin and rebase all currently open PR branches to ensure they are up to date."
- "Build a production branch called 'release-candidate' that includes all my open PRs and the 'hotfix-custom-auth' patch, using auto-resolve for any conflicts."
- "Review my last 10 closed PRs and generate a summary report of which ones contain code I should migrate to my permanent local patch directory."
Tips & Limitations
- Orchestrator Pattern: Always allow the main agent to spawn a subagent (Worker) to handle this skill. Avoid trying to force inline execution, as large repositories with dozens of PRs can exceed standard context windows.
- Conflict Resolution: When using the --auto-resolve flag, ensure you have sufficient tokens, as this triggers AI-subagents to read, modify, and commit code fixes autonomously.
- Monitoring: The orchestrator will check worker progress every 4 minutes. If a task stalls, the system will automatically kill and restart the worker, guaranteeing high reliability for long-running synchronization tasks.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-glucksberg-fork-manager": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, external-api, code-execution
Related Skills
issue-prioritizer
Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.
pr-ship
Pre-ship risk report for OpenClaw PRs. Dynamically explores the codebase to assess module risk, blast radius, and version-specific gotchas. Scores each finding by severity (🟢/🟡/🔴). Updated frequently with the latest OpenClaw version context — run `clawhub update pr-ship` regularly to stay current.
cross-ref
Cross-reference GitHub PRs and issues to find duplicates and missing links. Spawns parallel Sonnet subagents to semantically analyze the last N PRs and issues, finding PRs that solve the same problem (duplicates) and issues resolved by open PRs but not yet linked. Groups findings into thematic clusters, scores them by actionability, and offers rate-limited commenting or bulk actions (close, label). Use this skill when the user wants to find duplicate PRs, link issues to PRs, clean up a repo's cross-references, or audit PR/issue relationships. Also useful when the user says things like "find related PRs", "which PRs fix this issue", "are there duplicate PRs", "link issues and PRs", or "audit cross-references".
anti-pattern-czar
Detect and fix TypeScript error handling anti-patterns with state persistence and approval workflows. Use when scanning a codebase for silent error failures, empty catches, promise swallowing, or unlogged errors. Supports five modes — scan (detect all issues), review (interactive fix session), auto (batch fix with guardrails), resume (continue from last session), report (show progress). Triggers on phrases like 'scan for anti-patterns', 'fix error handling', 'find empty catches', 'anti-pattern czar', or 'check error handling'.
pr-review
Find and fix code issues before publishing a PR. Single-pass review with auto-fix. Use when reviewing code changes before submission or auditing existing code for bugs/security. Don't use when running a coding agent to write code (use coding-agent) or checking GitHub CI status (use github).