How do I install the Issue skill?

Run npx skillmds@latest add floomhq/issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

floomhq (@floomhq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Issue by floomhq — Agent Skill

Name: Issue
Author: floomhq

Issue

GitHub issue management with multi-account support. Creates, lists, views, and closes issues with correct labels and conventions per project. Use when user says "create issue", "file bug", "issue for X", "list issues", "open issues", "triage", or "close issue".

floomhq bff2a18 2.6 KB Updated Sep 17, 2026

File contents

GitHub Issue Management

Manage GitHub issues across multiple accounts. Always use GitHub Issues, never ISSUES.md files.

Step 1: Detect Project and Switch Account

Determine which project from context (cwd, user mention). If ambiguous, ask.

Project	Account alias	Repo
project-a	`gh-project-a`	auto-detect from cwd
project-b	`gh-project-b`	`org/repo-name`
personal	`gh-personal`	auto-detect from cwd

Check current account first:

gh auth status

Switch to correct account before any gh command.

Step 2: Execute the Right Command

Create Issue

gh issue create --title "..." --label "LABELS" --body "BODY"

For projects with strict labeling: ALWAYS include required labels. Ask the user for priority if not provided.

For repos you're not in the directory of:

gh issue create --repo org/repo-name --title "..." --body "..."

List Issues

gh issue list --state open
gh issue list --label "P0" --state open
gh issue list --label "P0,frontend" --state open

View Issue

gh issue view 123

Close Issue

Always close with a comment explaining the resolution:

gh issue close 123 --comment "Fixed in commit abc123. Verified on live site."

Label Conventions

Example: Priority + Area labeling

Type	Labels
Priority	`P0` (critical), `P1` (high), `P2` (medium), `P3` (low)
Area	`frontend`, `backend`, `pipeline`

Always include one from each group. If user doesn't specify priority, ask.

Issue Body Format

For bug reports:

**Steps to reproduce:**
1.
2.

**Expected:**

**Actual:**

**Context:** [URL, env, user account if relevant]

For feature requests:

**Problem:**

**Proposed solution:**

**Acceptance criteria:**
- [ ]

Keep bodies concise. No filler. Facts only.

Rules

NEVER use ISSUES.md files. GitHub Issues only.
ALWAYS verify the active account matches the project before any write operation.
When closing an issue: ALWAYS include a comment with the fix reference.
If the project cannot be determined from context, ask before proceeding.

---name: issuedescription: GitHub issue management with multi-account support. Creates, lists, views, and closes issues with correct labels and conventions per project. Use when user says "create issue", "file bug", "issue for X", "list issues", "open issues", "triage", or "close issue".---# GitHub Issue ManagementManage GitHub issues across multiple accounts. Always use GitHub Issues, neverISSUES.md files.## Step 1: Detect Project and Switch AccountDetermine which project from context (cwd, user mention). If ambiguous, ask.| Project | Account alias | Repo ||---------|--------------|------|| project-a | `gh-project-a` | auto-detect from cwd || project-b | `gh-project-b` | `org/repo-name` || personal | `gh-personal` | auto-detect from cwd |Check current account first:```bashgh auth status```Switch to correct account before any `gh` command.## Step 2: Execute the Right Command### Create Issue```bashgh issue create --title "..." --label "LABELS" --body "BODY"```For projects with strict labeling: ALWAYS include required labels.Ask the user for priority if not provided.For repos you're not in the directory of:```bashgh issue create --repo org/repo-name --title "..." --body "..."```### List Issues```bashgh issue list --state opengh issue list --label "P0" --state opengh issue list --label "P0,frontend" --state open```### View Issue```bashgh issue view 123```### Close IssueAlways close with a comment explaining the resolution:```bashgh issue close 123 --comment "Fixed in commit abc123. Verified on live site."```## Label Conventions### Example: Priority + Area labeling| Type | Labels ||------|--------|| Priority | `P0` (critical), `P1` (high), `P2` (medium), `P3` (low) || Area | `frontend`, `backend`, `pipeline` |Always include one from each group. If user doesn't specify priority, ask.## Issue Body FormatFor bug reports:```**Steps to reproduce:**1.2.**Expected:****Actual:****Context:** [URL, env, user account if relevant]```For feature requests:```**Problem:****Proposed solution:****Acceptance criteria:**- [ ]```Keep bodies concise. No filler. Facts only.## Rules- NEVER use ISSUES.md files. GitHub Issues only.- ALWAYS verify the active account matches the project before any write operation.- When closing an issue: ALWAYS include a comment with the fix reference.- If the project cannot be determined from context, ask before proceeding.

Frequently asked questions