detect-project-from-epic

Detects Epic project labels via GitHub API during repository migrations.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill detect-project-from-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-project-from-epic
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/biz/discovery/skills/detect-project-from-epic
Command: npx skills add https://github.com/semicolon-devteam/semo --skill detect-project-from-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

이식될 에픽의 원본 프로젝트 라벨을 자동으로 감지해 새 에픽에 동일한 프로젝트를 적용합니다.

Core Features & Use Cases

  • 프로젝트 라벨 매핑: 오피스/랜드/정치판/코인톡
  • 감지 실패 시 수동 선택 안내

Quick Start

원본 에픽에서 프로젝트 라벨을 감지합니다.

Frequently Asked Questions about detect-project-from-epic

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

FAQPage Schema
How do I automatically detect project labels when migrating epics between repositories?

Detect project labels by querying the source epic's labels via the GitHub API, filtering for known project categories (오피스, 랜드, 정치판, 코인톡), and mapping them to internal project keys (cm-office, cm-land, cm-politics, cm-cointalk). This preserves consistent project categorization during migration workflows between repositories like command-center to docs.

What project labels does the epic migration detection support?

The skill detects four project labels: 오피스 (cm-office), 랜드 (cm-land), 정치판 (cm-politics), and 코인톡 (cm-cointalk). During migration, it automatically identifies which label is attached to the source epic and maps it to the corresponding internal project key for application to the target epic.

What happens if the source epic has no project label during migration?

If project label detection fails, the skill provides guidance for manual selection. Users can then choose the appropriate project category themselves to ensure the migrated epic receives correct project assignment in the new repository.

Can I use this for cross-repository epic migration workflows?

Yes, the skill is designed specifically for migration workflows between repositories. It queries GitHub API labels on the source epic and returns structured detection results that enable downstream labeling in the target repository, supporting migrations like command-center to docs.

What input data does the project detection require?

The skill requires the source epic's GitHub labels as input. It queries these labels via the GitHub API, filters for recognized project labels, and returns a structured detection result containing the mapped internal project key for downstream labeling operations.