aget-promote-issue

/aget-promote-issue

Promote issues from the private tracker (gmelli/aget-aget) to the public tracker (aget-framework/aget) through governed content sanitization and principal approval. Prevents private information leakage at the promotion boundary.

Purpose

The private-first routing model (L638) means all issues start in gmelli/aget-aget. Some need public visibility. This skill governs that boundary crossing with content sanitization (R-ISSUE-011), principal approval, and source traceability.

Input

issue_number - The private issue number to promote (required)

Examples:

• /aget-promote-issue #834 — Promote issue 834
• /aget-promote-issue #834 --dry-run — Preview sanitized content without filing

Execution

Step 1: Read Source Issue

gh issue view {issue_number} --repo gmelli/aget-aget --json title,body,labels,state

Verify: issue exists, is open, belongs to gmelli/aget-aget.

Step 2: Content Sanitization

Scan title and body for private patterns:

Pattern	Example	Action
Private agent names	private-*-aget, private-*-AGET	BLOCK
Private repo refs	gmelli/*	BLOCK
Fleet size	"32 agents", "40 agents"	BLOCK
Internal project IDs	FLEET-*-###	BLOCK
Session references	SESSION_2026-*	BLOCK

If ANY pattern detected: display matches, ask user to revise source issue first.

Step 3: Draft Promoted Content

• Title: Sanitized version of source title
• Body: Sanitized body + footer: _Promoted from internal tracker._
• Labels: Transfer type:* and domain:* labels. Do NOT transfer owner:* or status:*.

Step 4: Principal Approval Gate

Display drafted content and checklist:

=== Promotion Preview: #{issue_number} ===

Title: {sanitized_title}
Body: {sanitized_body}
Labels: {transferred_labels}
Destination: aget-framework/aget

Checklist:
- [ ] Principal approval (R-ISSUE-011)
- [ ] Content sanitization passed (R-ISSUE-012)
- [ ] Source traceability included (R-ISSUE-013)
- [ ] Label mapping complete (R-ISSUE-014)

Proceed? [Y/N]