log-issue

Creates on-disk GitHub issue drafts with YAML frontmatter and body skeleton.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/opendatadiscovery/odd-team --skill log-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-issue
Source: https://github.com/opendatadiscovery/odd-team/tree/main/.claude/skills/log-issue
Command: npx skills add https://github.com/opendatadiscovery/odd-team --skill log-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft upstream GitHub issue drafts on disk, enabling consistent, review-ready artifacts without prematurely filing to GitHub.

Core Features & Use Cases

  • Create on-disk drafts under issues/{repo}/{PREFIX}-NNN.md with paste-ready frontmatter and skeleton body.
  • Prevent accidental filing by storing drafts in workspace until human submission.
  • Cite context from navigation/repos.yaml and backlog items to support discovered_during data.

Quick Start

Provide the target repo and optional title to generate the next draft and save it under issues/{repo}/{PREFIX}-NNN.md.

Frequently Asked Questions about log-issue

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

FAQPage Schema
How do I create a draft GitHub issue on disk before filing it to a repository?

To create a draft GitHub issue on disk, this Skill generates a paste-ready markdown file with required YAML frontmatter and body skeleton at issues/{repo}/{PREFIX}-NNN.md. It ensures structured, review-ready artifacts without prematurely filing to GitHub.

Can I automatically file bug reports or feature requests to GitHub from a backlog?

No, you cannot automatically file bug reports or feature requests to GitHub. The Skill explicitly refuses to file to GitHub automatically, instead storing review-ready draft issues on disk for targeted repositories until human submission.

What is the best way to structure backlog item transitions into review-ready issue drafts?

The best way to structure backlog item transitions into review-ready issue drafts is by generating on-disk files under issues/{repo}/{PREFIX}-NNN.md. These drafts include paste-ready frontmatter and cite context from navigation/repos.yaml to support discovered_during data.

Does this workflow require any external dependencies to draft upstream GitHub issues?

No, drafting upstream GitHub issues requires no external dependencies. The Skill operates independently to create structured draft files on disk, preventing accidental filing by storing them in your workspace until manual submission.

How do I generate the next draft issue for a specific repo using automation?

To generate the next draft issue using automation, provide the target repository and an optional title. The Skill automatically saves the new draft under issues/{repo}/{PREFIX}-NNN.md with the correct numbering and required skeleton.