메뉴
Use to convert an Obsidian note into a GitHub Issue. Triggers on "노트로 이슈 만들어", "이슈로 변환", "이거 이슈로", "노트 이슈화". Only use when user explicitly references an Obsidian note as the source. For creating issues from conversation context (without a note), use create-issue instead.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | note-to-issue |
| description | Use to convert an Obsidian note into a GitHub Issue. Triggers on "노트로 이슈 만들어", "이슈로 변환", "이거 이슈로", "노트 이슈화". Only use when user explicitly references an Obsidian note as the source. For creating issues from conversation context (without a note), use create-issue instead. |
Delegate to archivist agent (sonnet):
A) Read note — scripts/vault-read.sh read --path {NOTE_PATH} → parse frontmatter + body
B) Project info — frontmatter project field or scripts/identify-project.sh
C) Assignee — gh api user --jq '.login'
issue-type is missing → ask for type (feature / task / bug)issue-type: task → ask for parent Feature issue numberref/issue-template-mapping.mdgh issue create --repo {OWNER}/{PROJECT} --title "{title}" --body "{body}" --assignee {ASSIGNEE}> 🤖 **AI created** — Converted from Obsidian notegh project item-add {PROJECT_NUMBER} --owner {OWNER} --url {ISSUE_URL}gh issue edit {N} --repo {REPO} --add-parent {PARENT_N}scripts/vault-update.sh property-set --path {NOTE_PATH} --key issue --value "#{N}"scripts/vault-update.sh property-set --path {NOTE_PATH} --key status --value issuedscripts/vault-update.sh append --path {NOTE_PATH} --content "---\n> GitHub Issue: [#{N}]({ISSUE_URL})"ref/issue-template-mapping.md — template mapping by issue typeref/frontmatter-schema.md — frontmatter field definitionsissue field already has a value, warn about duplicate and do not proceed without user confirmationissue-type is missing, ask the user before proceedingAI created markerLoaded automatically at session start. Teaches the orchestrator how to route requests to skills and agents. Do not invoke manually.
Use when the user wants to explore an idea, design an approach, or think through a problem before implementing. Triggers on "고민", "논의", "아이디어", "brs".
Use when code review is needed. Triggers on "코드 리뷰", "리뷰해줘", "code review", or at completion of implementation.
Use to harvest `debt:` markers across the repo into a debt ledger and optionally persist it to the Obsidian vault. Triggers on "부채", "기술부채", "debt", "지름길 정리", "/debt". Read-only — does not modify code.
Use when the user wants to run an implementation plan. Triggers on "실행해줘", "구현해줘", "시작해줘", "execute", or after plan approval.
Implement an entire Figma page as Android Jetpack Compose screens by auto-splitting into frames with visual verification. Use whenever a user shares a figma.com/design URL and wants the page built as Compose code. Triggers on '안드로이드 피그마', 'Android Figma', 'Compose 구현'. Covers any multi-frame page. Does NOT apply to Figma asset downloads or single component edits.