issue-file

Create or update GitHub issues from a markdown file via --body-file.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill issue-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-file
Source: https://github.com/matsen/bipartite/tree/main/skills/issue-file
Command: npx skills add https://github.com/matsen/bipartite --skill issue-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update GitHub issues from a markdown file using its body content.

Core Features & Use Cases

  • Create issues from markdown file contents using the --body-file flag to populate the issue body verbatim.
  • Update existing issues by referencing the issue number or context from the conversation.
  • Enforce safety: do not auto-assign unless explicitly requested by the user; respect content boundaries.

Quick Start

Run the skill with a path to a markdown file to create or update a GitHub issue using the --body-file flag.

Frequently Asked Questions about issue-file

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

FAQPage Schema
How do I create a GitHub issue from a markdown file?

You can create a GitHub issue from a markdown file by using the --body-file flag to ingest the file verbatim, populating the issue body directly with the markdown content.

Can I update existing GitHub issues using a markdown body file?

Yes, you can update existing GitHub issues by referencing the issue number or conversation context, allowing the workflow to determine whether to apply an update versus creating a new issue.

Does creating issues with a markdown body file auto-assign users?

No, creating issues with a markdown body file does not auto-assign users unless explicitly requested, enforcing safety by respecting content boundaries and preventing automatic assignment.

What is the best way to automate GitHub issue creation from markdown drafts?

Automating GitHub issue creation from markdown drafts is best handled by using the --body-file flag to ingest the file verbatim, ensuring the issue body matches the markdown draft content exactly.

How does the workflow determine whether to create or update a GitHub issue?

The workflow determines whether to create or update a GitHub issue by checking recent conversation context and existing issue references, applying updates to existing issues found via conversation context.