file-issue

Creates a single ad hoc tracker issue as a Note with labels and confirmation.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill file-issue-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-issue
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/file-issue
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill file-issue-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It captures ad hoc findings, bugs, and ideas that surface outside milestone planning as properly formatted tracker issues, so nothing gets lost and no half-formed issue enters the delivery pipeline. ## Core Features & Use Cases - Note-style issue drafting: Builds the title and body in the plugin's mandatory issue template with an empty acceptance-criteria section, reserving refinement for the triage step. - Label and forge handling: Assigns exactly one area label plus a type label matching the title, reads existing labels from Gitea or GitHub, and creates missing labels only after confirmation. - Confirmation gate: Presents the full draft via an interactive question and writes nothing to the tracker until the user approves. - Use Case: While reviewing code you spot a bug unrelated to your current task; invoke the skill with a short description and it files a labeled issue in the tracker and returns its number and URL. ## Quick Start Ask the assistant to file an issue describing the bug or idea you want recorded in the tracker.

Frequently Asked Questions about file-issue

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

FAQPage Schema
How do I file a quick bug issue without planning a milestone?

Invoke the skill with a short description of the bug or finding. It drafts the issue in the project's mandatory template, proposes labels, asks for your confirmation, and only then creates the issue in the tracker, returning its number and link.

What issue trackers does this skill support?

It supports Gitea through deferred MCP tools loaded via ToolSearch and GitHub through bundled gh shell scripts invoked with bash. The forge type, owner, and repository come from the Workflow section of the project's CONTRIBUTING.md.

Why does the created issue have empty acceptance criteria?

The skill intentionally files every issue as a Note capturing intent or observation, leaving acceptance criteria as a bare heading. Filling criteria is the job of the separate triage-issue skill, which promotes the Note into a code-anchored Task.

Can I assign a milestone when filing an ad hoc issue?

Only on explicit request. The skill looks up the milestone by name first and never creates a new one, since milestone creation belongs to plan-milestone. A Note in a milestone still needs triage-issue before it can be dispatched.

What happens if the project has no workflow configuration?

The skill stops without creating anything and tells the user the project lacks a Workflow section in CONTRIBUTING.md, offering to run init-workflow instead. It never guesses configuration values such as label taxonomies or forge settings.