issue

File GitHub issues from conversation triggers with Type labels and domain cues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matthewfrazier/mobissh --skill issue-matthewfrazier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/matthewfrazier/mobissh/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/matthewfrazier/mobissh --skill issue-matthewfrazier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically file GitHub issues from in-conversation observations without interrupting the current workflow.

Core Features & Use Cases

  • Create issues in the background from conversation triggers such as bug:, feature:, fix:, or /issue.
  • Apply the appropriate Type label and domain cues based on the project's taxonomy.
  • Route the request through the issue-manager agent to file the issue without blocking the conversation.

Quick Start

File a GitHub issue from the current chat without interrupting your workflow.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I automatically create GitHub issues from chat without interrupting my workflow?

You can automatically create GitHub issues in the background by triggering the conversation with prefixes like bug:, feature:, feat:, fix:, chore:, or /issue, which files the issue without blocking your current chat workflow.

How does automatic GitHub issue labeling work from conversation triggers?

Automatic GitHub issue labeling works by consulting the .claude/process.md file and SKILL.md frontmatter metadata to apply a proper Type label and domain cues according to the project's specific taxonomy when an issue is triggered.

Can I file bug reports and feature requests in GitHub directly from my development chat?

Yes, you can file bug reports and feature requests directly from your development chat by using the bug: or feature: prefixes, which route the request through the issue-manager agent to file the issue in the background.

What is the best way to capture background tasks as GitHub issues while coding?

The best way to capture background tasks as GitHub issues while coding is using prefixes like chore: or fix: in the conversation, which delegates the issue filing to a background agent so development continues uninterrupted.

Do I need a specific agent setup to file GitHub issues in the background?

Filing GitHub issues in the background requires the issue-manager agent to be available, which handles the delegation of the issue creation process without blocking the current conversation workflow.