workbench-sync — dotnet-tool workbench-sync, workbench, community, dotnet-tool, ide skills, github, task-tracking

v1.0.0
GitHub

About this Skill

Ideal for Development Agents utilizing GitHub for project management and requiring seamless issue and documentation synchronization. Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.

# Core Topics

dotnet-tool github task-tracking
incursa incursa
[0]
[0]
Updated: 2/20/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
51
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents utilizing GitHub for project management and requiring seamless issue and documentation synchronization. Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.

Core Value

Empowers agents to synchronize local work items with GitHub issues, branches, and PRs, leveraging CLI tools and configuring settings like github.owner and git.defaultBaseBranch, while ensuring authenticated access via gh auth login.

Ideal Agent Persona

Ideal for Development Agents utilizing GitHub for project management and requiring seamless issue and documentation synchronization.

↓ Capabilities Granted for workbench-sync

Importing missing GitHub issues into local work items for unified project tracking
Creating missing GitHub issues for active work items to maintain consistency
Syncing doc backlinks and front matter for accurate documentation
Automating branch creation for active items to streamline development workflows

! Prerequisites & Limits

  • Requires GitHub authentication via gh auth login
  • Needs configuration of .workbench/config.json settings
  • Limited to GitHub as the project management platform

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is workbench-sync?

Ideal for Development Agents utilizing GitHub for project management and requiring seamless issue and documentation synchronization. Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.

How do I install workbench-sync?

Run the command: npx killer-skills add incursa/workbench/workbench-sync. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for workbench-sync?

Key use cases include: Importing missing GitHub issues into local work items for unified project tracking, Creating missing GitHub issues for active work items to maintain consistency, Syncing doc backlinks and front matter for accurate documentation, Automating branch creation for active items to streamline development workflows.

Which IDEs are compatible with workbench-sync?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for workbench-sync?

Requires GitHub authentication via gh auth login. Needs configuration of .workbench/config.json settings. Limited to GitHub as the project management platform.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add incursa/workbench/workbench-sync. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use workbench-sync immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

workbench-sync

Install workbench-sync, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Key settings

  • .workbench/config.json: github.owner, github.repository, github.host, git.defaultBaseBranch.
  • Ensure gh auth login is complete before syncing issues.

Core workflows

  1. Import missing GitHub issues into local work items.
  2. Create missing GitHub issues for active work items.
  3. Create branches for active items.
  4. Sync doc backlinks and front matter.

Commands

Dry-run sync:

bash
1workbench.ps1 sync --dry-run

Sync a specific item and prefer GitHub content:

bash
1workbench.ps1 item sync --id TASK-0001 --prefer github

Bulk sync (local wins on conflicts):

bash
1workbench.ps1 sync --items

Import unlinked GitHub issues (slower):

bash
1workbench.ps1 sync --items --import-issues

Sync doc backlinks (include done items when needed):

bash
1workbench.ps1 doc sync --all
2workbench.ps1 doc sync --all --include-done

Output

  • New work items from GitHub issues.
  • New GitHub issues and branches for active work items.
  • Updated doc backlinks and front matter.

Guardrails

  • Use --dry-run before creating issues or branches.
  • workbench.ps1 sync defaults to linked work items only; use --import-issues to pull unlinked GitHub issues.
  • Terminal items (done/dropped) do not create issues or branches by default.
  • Sync is not a replacement for specs/ADRs; create or update them during planning.

Related Skills

Looking for an alternative to workbench-sync or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer