Export skill outputs to issue trackers (GitHub/Forgejo/Linear) #10

New issue

Closed

opened 2026-04-24 02:59:35 +00:00 by frank · 1 comment

frank commented

2026-04-24 02:59:35 +00:00

Owner

Summary

Push skill outputs (scope items, tech debt, security findings, sprint items) directly to issue trackers as labeled issues.

Why

Skill outputs live in JSON sidecars. For actionable tracking, items need to land in the developer's actual issue tracker.

Implementation

Support GitHub, Forgejo, and Linear APIs
Map categories to labels automatically
Idempotent: no duplicates on re-run

Effort

Medium (1-3 days)

## Summary Push skill outputs (scope items, tech debt, security findings, sprint items) directly to issue trackers as labeled issues. ## Why Skill outputs live in JSON sidecars. For actionable tracking, items need to land in the developer's actual issue tracker. ## Implementation - Support GitHub, Forgejo, and Linear APIs - Map categories to labels automatically - Idempotent: no duplicates on re-run ## Effort Medium (1-3 days)

frank added this to the v1.2 � Integrations & Automation milestone

2026-04-24 02:59:35 +00:00

frank added the

priority:medium

integration

enhancement

labels

2026-04-24 02:59:35 +00:00

frank referenced this issue from a commit

2026-04-24 19:47:22 +00:00

feat: add issue tracker export for skill outputs

frank closed this issue

2026-04-24 19:47:22 +00:00

frank commented

2026-04-24 19:53:29 +00:00

Author

Owner

Implemented in 665f24b. export_issues.py supports GitHub and Forgejo APIs, reads scope/techdebt/security/sprint sidecars, auto-creates labels, and tracks exports idempotently via .exported.json.

Implemented in 665f24b. export_issues.py supports GitHub and Forgejo APIs, reads scope/techdebt/security/sprint sidecars, auto-creates labels, and tracks exports idempotently via <slug>.exported.json.