skills.rest
waltcow
waltcowCOMMUNITY
Explore all skills by this author →
GitHub

multica-working-on-issues

Coordinate Multica issue work by reading linked PR state and metadata keys via pull-requests CLI.

1|Updated May 24, 2026
Search Tags:#automation#metadata#issues#workflows#pull-requests#multica
One-click install
npx skills add https://github.com/waltcow/multica --skill multica-working-on-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multica-working-on-issues
Source: https://github.com/waltcow/multica/tree/main/server/internal/service/builtin_skills/multica-working-on-issues
Command: npx skills add https://github.com/waltcow/multica --skill multica-working-on-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When an issue is active and the runtime brief does not encode all contracts, this skill helps you apply the product contracts, interpret PR linking vs close intent, read the real state of linked PRs using the multica issue pull-requests CLI, and understand which metadata keys are high-signal. It also clarifies which status changes on the server trigger agent work and how sub-issue creation with todo vs backlog affects immediate execution.

Core Features & Use Cases

  • Interpret PR linking vs close intent and determine how they affect issue state.
  • Read a linked PR's real state with the pull-requests CLI and verify CI status.
  • Identify and surface high-signal metadata keys (e.g., pr_url, pr_number, pipeline_status) for downstream tasks.
  • Understand and control enqueue behavior via status transitions (todo vs backlog) and sub-issue creation rules.
  • Align issue workflows with product contracts not encoded by the runtime brief.

Quick Start

Apply the product contracts for a Multica issue and read the linked PR state using the pull-requests CLI to verify the current status and link relationships.

Frequently Asked Questions about multica-working-on-issues

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

FAQPage Schema
How do I check the real state of a linked pull request for an active issue?▼

To check the real state of linked pull requests, use the pull-requests CLI to read PR metadata, verify CI status, and interpret whether the link implies active work or close intent.

What is the difference between PR linking and close intent in issue workflows?▼

PR linking indicates an active code association where the issue remains open, while close intent signals the PR should resolve the issue upon merge. This distinction affects issue state transitions and agent workflow triggers.

Which metadata keys are high-signal for tracking pull request workflows?▼

High-signal metadata keys include pr_url, pr_number, and pipeline_status. These keys surface the real PR state and CI results needed for downstream workflow tasks and product contract alignment.

How do sub-issue creation rules affect execution with todo vs backlog status?▼

Sub-issue creation with todo status triggers immediate agent execution, while backlog status defers it. Status transitions control enqueue behavior and determine whether the runtime activates work automatically.

How do I align issue workflows with product contracts not encoded by the runtime brief?▼

To align issue workflows with unencoded product contracts, apply contract guidance to interpret PR mappings, read linked PR state via CLI, and manage status side effects for correct workflow execution.

When do I need to apply product contracts for issue workflows beyond the runtime brief?▼

You need to apply product contracts when an issue is active and PRs are linked, but the runtime brief does not encode all required rules for PR state interpretation, metadata tracking, and status-driven enqueue behavior.

Related Skills

Explore More Software Engineering Skills→
kinneyyankinneyyan
2

code-review

Analyze git changes to identify critical and high-priority issues.

Community
Advanced
ChegginCheggin
1

github-state-manager

Automate GitHub Issue and Project state transitions with audit trails.

Community
Advanced
multica-aimultica-ai
44.9k

multica-working-on-issues

Automate issue-PR contract enforcement and link/close intents across Multica workflows.

Official
Intermediate
kubiyabotkubiyabot
16

azure

Manage Azure resources via the native az CLI.

Official
Advanced