note-to-issue

Convert Obsidian notes into GitHub Issues using frontmatter and body content.

4|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill note-to-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: note-to-issue
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/note-to-issue
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill note-to-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian notes with planning or task content can be manually copied into GitHub Issues, leading to fragmentation and lost context. This skill automates the transformation by reading the note's frontmatter and body to create a structured issue with metadata and links.

Core Features & Use Cases

  • Read Obsidian notes and extract metadata to create consistent GitHub issues.
  • Map frontmatter fields to issue properties, auto-link to project boards, assign owners, and update the source note with the created issue reference.
  • Use Case: When you need to turn planning notes or task descriptions into trackable GitHub issues for collaboration and progress tracking.

Quick Start

Trigger the skill with the path to the Obsidian note you want to convert and let it create and link the corresponding GitHub Issue.

Frequently Asked Questions about note-to-issue

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

FAQPage Schema
How do I turn Obsidian notes into GitHub Issues automatically?

To turn Obsidian notes into GitHub Issues, you can use automation to read the note's frontmatter and body, mapping fields directly to issue titles, bodies, and project properties. This prevents manual copying and context loss.

Can I map Obsidian frontmatter fields to GitHub issue properties?

Yes, Obsidian frontmatter fields can be mapped directly to GitHub issue properties. The automation reads your frontmatter to populate the issue title, body, and fields, and can even assign owners based on vault discovery.

How do I link a created GitHub issue back to my Obsidian vault?

You can link a created GitHub issue back to your Obsidian vault through automated vault updates. After issue creation, the source note is updated with the corresponding GitHub issue reference for bidirectional tracking.

Does this issue creation process support linking to GitHub project boards?

Yes, the issue creation process supports optional GitHub project association. You can configure project board linking and assignees by defining them within the Obsidian note's frontmatter prior to conversion.

What is the best way to track Obsidian planning notes in GitHub?

The best way to track Obsidian planning notes in GitHub is by converting task descriptions into structured issues. This applies when notes describe tasks, features, or bugs, ensuring they are tracked on a project board.