temporary-id-safe-output

Generates and resolves temporary IDs for linking workflow issues before real numbers exist.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill temporary-id-safe-output-kaushal-waygood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: temporary-id-safe-output
Source: https://github.com/kaushal-waygood/agentic-self-healing-ci/tree/main/skills/temporary-id-safe-output
Command: npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill temporary-id-safe-output-kaushal-waygood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an agent needs to create a parent issue and immediately link sub-issues to it in the same workflow run, the agent doesn't know the actual issue number until the create_issue job completes. Temporary IDs bridge this gap by allowing the agent to use placeholder IDs that are resolved to actual issue numbers at execution time.

Core Features & Use Cases

Temporary IDs follow the pattern aw_[A-Za-z0-9]{3,8} where:

  • aw_ is a fixed prefix identifying agentic workflow temporary IDs
  • XXXXXXXX is a 3-8 character alphanumeric string (A-Za-z0-9) Example: aw_abc, aw_abc123, aw_Test123
  • Implementation Components: Shared module temporary_id.cjs at pkg/workflow/js/temporary_id.cjs for core utilities
  • Producer: create_issue outputs a temporary_id_map that maps temp IDs to issue numbers
  • Consumer: downstream safe-output jobs load the map and resolve IDs to real issue numbers

Quick Start

Configure a workflow to generate temporary IDs, map them to real issue numbers, and resolve placeholders to link related issues within a single run.

Frequently Asked Questions about temporary-id-safe-output

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

FAQPage Schema
How do I link sub-issues to a parent issue in a single GitHub Actions workflow run before the real issue number exists?

Linking sub-issues to a parent issue in a single GitHub Actions workflow run requires using temporary IDs as placeholders. Downstream jobs resolve these temporary IDs to actual issue numbers once the parent issue creation job completes.

What is a temporary ID and how does it work for issue linking in automation?

A temporary ID is a placeholder following the pattern `aw_[A-Za-z0-9]{3,8}` used for issue linking in automation. It allows agents to map parent-child relationships during a workflow run until real issue numbers are available for resolution.

How do I generate and resolve temporary IDs to map placeholder values to real GitHub issue numbers?

Generating and resolving temporary IDs to map placeholder values to real GitHub issue numbers involves a producer job creating a `temporary_id_map`, which downstream consumer jobs load to resolve the placeholders during execution.

Can I use temporary IDs for issue linking across multiple downstream jobs in a DevOps pipeline?

You can use temporary IDs for issue linking across multiple downstream jobs in a DevOps pipeline through environment propagation. The workflow propagates the temporary ID map to downstream jobs so they can resolve parent-child relationships safely.

What happens to workflow issue linking when a temporary ID remains unresolved at execution time?

When a temporary ID remains unresolved at execution time, the workflow issue linking process relies on non-fatal failure handling. This ensures the workflow continues running safely without crashing due to unresolved placeholder IDs.