issue-auto-sync

Parse commit messages to update issue statuses via GitHub and Gitea APIs.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill issue-auto-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-auto-sync
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/issue-auto-sync
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill issue-auto-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious process of manually linking code commits and project artifacts to issues in your tracking system, ensuring your issue tracker accurately reflects development progress.

Core Features & Use Cases

  • Automated Issue Linking: Detects issue references in commit messages and artifact metadata.
  • Status Updates: Automatically updates issues with progress, closes them upon completion, and notifies blockers.
  • Use Case: After committing code that fixes a bug, this Skill automatically finds the corresponding issue number in your commit message (e.g., "Fixes #123") and updates the issue's status to "Closed" on GitHub or Gitea.

Quick Start

Run the issue-auto-sync skill to automatically update linked issues after your last commit.

Frequently Asked Questions about issue-auto-sync

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

FAQPage Schema
How do I automatically link commit messages to issue tracker updates?

Automated issue linking parses commit messages for predefined issue ID patterns and updates issue status, adds comments, or closes them via API integrations with platforms like GitHub and Gitea.

Can I automatically close GitHub or Gitea issues from a commit message?

Yes, committing code with predefined issue references like "Fixes #123" triggers the sync to automatically update the issue's status to "Closed" on GitHub or Gitea platforms.

How does parsing artifact metadata work for issue tracking synchronization?

Issue tracking synchronization works by detecting issue references within commit messages and artifact metadata, then automatically updating linked issues with progress, closure statuses, and blocker notifications.

Do I need API integrations configured to sync issues across commits and artifacts?

Yes, API integrations with GitHub or Gitea are required to automatically push parsed issue status updates, comments, and closures directly to your development tracking platforms.

What is the best way to automate issue status updates based on development activities?

Automating issue status updates is best handled by parsing commit messages and artifact references to identify issue IDs and push status changes via platform API integrations.

Why does my commit message issue ID pattern fail to update the issue tracker status?

Issue tracker status updates fail when commit messages do not match the predefined issue ID patterns required for parsing, preventing the API integration from identifying and updating the linked issue.