skills.rest
multica-ai
multica-aiOFFICIAL
Explore all skills by this author →
GitHub

multica-working-on-issues

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

44.9k|5.7k|Updated Jan 13, 2026
Search Tags:#workflow#metadata#issue#linking#pull-requests#multica#close-intent
One-click install
npx skills add https://github.com/multica-ai/multica --skill multica-working-on-issues-multica-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multica-working-on-issues
Source: https://github.com/multica-ai/multica/tree/main/server/internal/service/builtin_skills/multica-working-on-issues
Command: npx skills add https://github.com/multica-ai/multica --skill multica-working-on-issues-multica-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams coordinate the enforcement of product contracts between issues and their linked PRs, clarifying the distinction between PR linking and close intent, and ensuring consistent behavior across workflows.

Core Features & Use Cases

  • PR linking vs close intent understanding and enforcement across issue-PR lifecycles.
  • Linked PR state reading using the pull-requests CLI to verify the real state of related work.
  • Metadata key guidance for high-signal fields used to drive automation and reporting.
  • Server-side contract enforcement for issue enqueueing, status transitions, and sub-issue creation semantics.

Quick Start

Start by reading the current trigger context, read linked PRs with multica issue pull-requests, and apply the product contracts described in this skill.

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 automate issue linking and close intent across pull requests?▼

Automate issue linking and close intent by applying server-side contracts that enforce PR state interpretation and status transitions across workflows. This Skill uses the references map to derive correct linkage behavior and metadata handling for issue-PR lifecycles.

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

PR linking associates a pull request with an issue, while close intent defines the semantic rules for when that issue should automatically close. This Skill clarifies and enforces that distinction to ensure consistent behavior across product contracts.

How do I read linked pull request state to verify related issue work?▼

Read linked pull request state by using the pull-requests CLI to verify the real runtime state of related work. This allows the workflow to accurately interpret PR states before applying issue enqueueing or status transition contracts.

Can I enforce server-side contracts for issue enqueueing and sub-issue creation?▼

Yes, you can enforce server-side contracts for issue enqueueing, status transitions, and sub-issue creation semantics. The Skill applies these contracts across runtime triggers spanning issues, PRs, and sub-issues to maintain consistent workflow behavior.

What metadata keys should I use to drive issue and PR automation?▼

Use high-signal metadata keys to drive automation and reporting across issue-PR workflows. This Skill provides metadata key guidance to ensure the correct fields are applied when enforcing product contracts and status transitions.

Related Skills

Explore More Software Engineering Skills→
waltcowwaltcow
1

multica-working-on-issues

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

Community
Advanced
jeremy-newhousejeremy-newhouse

wa:deploy-tracker

Update tracker issue statuses with commit and PR metadata after deployments.

Community
Intermediate
ncaqncaq
3

github

Retrieve GitHub file contents, issues, pull requests, and workflow statuses via MCP tools or gh CLI.

Community
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate