pace-sync

Synchronize devpace development state with GitHub, Linear, and Jira.

73|6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pace-sync
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-sync
Command: npx skills add https://github.com/arch-team/devpace --skill pace-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bridges the gap between your devpace development workflow and external project management and version control systems like GitHub, Linear, and Jira, ensuring seamless state synchronization.

Core Features & Use Cases

  • Bi-directional Synchronization: Push devpace status updates to external tools and pull external status changes back into devpace.
  • Integration Setup: Easily configure connections to GitHub, GitLab, Linear, and Jira.
  • Automated Linking: Link devpace Change Requests (CRs) to external issues automatically or manually.
  • CI/CD Integration: Monitor and trigger GitHub Actions workflows directly.
  • Use Case: When you push code changes in devpace, this Skill automatically updates the corresponding GitHub issue's status and adds a comment with a summary of the changes.

Quick Start

Use the pace-sync skill to set up synchronization with your GitHub repository.

Frequently Asked Questions about pace-sync

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

FAQPage Schema
How do I sync development state between devpace and external tools?

Development state sync between devpace and external tools is achieved through bi-directional updates, automatically pushing local status changes to external platforms and pulling remote updates back into your local environment.

Can I link devpace Change Requests directly to GitHub and Jira issues?

You can link devpace Change Requests to GitHub and Jira issues automatically or manually, establishing direct references that keep both systems connected and ensure state updates reflect accurately across platforms.

How does CI/CD integration work with GitHub Actions in this synchronization process?

CI/CD integration with GitHub Actions allows you to monitor and trigger workflows directly, automatically updating linked external issues with summaries of code changes when you push updates from your local development state.

What is the best way to set up initial connections to GitHub, Linear, and Jira for state synchronization?

The best way to set up state synchronization is by configuring connections to GitHub, Linear, and Jira directly within your development environment, establishing the authentication and mapping required for bi-directional updates.

Does state synchronization work with GitLab repositories as well as GitHub?

State synchronization supports GitLab repositories alongside GitHub, Linear, and Jira, allowing you to configure connections and maintain bi-directional updates across multiple external version control and project management systems.

Why are my bi-directional status updates failing to reflect in external project management tools?

Bi-directional status updates may fail if connections to external tools like GitHub or Jira are not properly configured, preventing the automated linking and state pushing mechanism from successfully mapping local Change Requests to remote issues.