Verified:Website 𝕏@anis_marrouchi GitHub

update-issue

Update GitHub or GitLab issues to reflect Ralf story state changes.

4|2|Updated Jan 20, 2026

Search Tags:#automation #github #issues #gitlab #update #workflows #tracking

One-click install

npx skills add https://github.com/anis-marrouchi/ralf --skill update-issue-anis-marrouchi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: update-issue
Source: https://github.com/anis-marrouchi/ralf/tree/main/skills/update-issue
Command: npx skills add https://github.com/anis-marrouchi/ralf --skill update-issue-anis-marrouchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically synchronize external issue trackers (GitHub/GitLab) with Ralf story state changes, reducing manual updates and keeping project management in sync with execution progress.

Core Features & Use Cases

Platform-aware updates: updates GitHub Issues or GitLab issues as stories change in Ralf.
Status synchronization: reflects on-start, on-complete, and on-blocked events with appropriate labels, comments, and optional closures.
Hook-ready integration: designed to run from lifecycle hooks and respect project-level configuration.

Quick Start

Use this skill to automatically update the linked GitHub or GitLab issue when a Ralf event occurs.

Frequently Asked Questions about update-issue

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

FAQPage Schema

How do I automatically update GitHub Issues when a task starts or completes?▼

You can automatically update GitHub Issues by running the update-issue skill during the Ralf execution lifecycle. It detects the platform, resolves issue references, and applies labels, comments, or closures based on story state changes.

Can I sync GitLab issues with Ralf story progress automatically?▼

Yes, the update-issue skill supports syncing Ralf story states with GitLab issues. It uses platform detection to apply appropriate labels, comments, and optional re-opening actions via glab or MCP commands.

What is the best way to keep issue trackers in sync with development workflows?▼

The best way to keep issue trackers in sync is using a hook-ready integration like the update-issue skill. It reflects on-start, on-complete, and on-blocked events from the Ralf lifecycle directly to GitHub or GitLab.

Do I need gh or glab installed to update issue trackers from Ralf?▼

Yes, you need either the gh or glab CLI tools installed to update issue trackers from Ralf. The update-issue skill relies on these tools or MCP commands to manage labels, comments, and issue closures.

How do I configure issue reference resolution for Ralf story synchronization?▼

You configure issue reference resolution and platform settings in the .ralf/config.json file. This configuration allows the update-issue skill to correctly map Ralf story state changes to the corresponding GitHub or GitLab issues.

Why are my issue tracker labels not updating when a story is blocked?▼

Labels may not update if the platform detection or issue reference resolution fails. Ensure your .ralf/config.json is correctly configured and that the update-issue skill is properly hooked into the Ralf lifecycle events.