agentleFS
alex-ilgayevalex-ilgayev/MCPSpy/.claude/skills/github-issue-creator/SKILL.md

github-issue-creator

Skill519 starsChanged 12 months agoApache-2.0View on GitHub

Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-creator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    pr-creator

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the gh issue CLI tool to create GitHub issues.

    line 14
  2. Very specific:

    Use standard prefixes: feat(component):, chore:, fix(component):

    line 18
  3. Distinctive:

    Keep titles concise and descriptive

    line 21
  4. Distinctive:

    Actionable scope: - should be implementable by a developer familiar with the codebase

    line 35

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Issue Creator Skill

Automates the creation of well-structured GitHub issues for the MCPSpy project.

Tools and Usage

Use the gh issue CLI tool to create GitHub issues. If the issue body is rather long, write it to a temporary markdown file and use the gh issue create --body-file <file> option.

Issue Naming Convention

  • Use standard prefixes: feat(component):, chore:, fix(component):
  • Component examples: library-manager, ebpf, mcp, http, output
  • Brackets are optional but recommended for clarity
  • Keep titles concise and descriptive

Examples

  • feat(library-manager): add support for container runtime detection
  • chore: update dependencies to latest versions
  • fix(ebpf): handle kernel version compatibility issues

Issue Content Guidelines

What to Include

  • High-level design notes - focus on the "what" and "why"
  • POC-level details - enough to get started, not exhaustive
  • Actionable scope - should be implementable by a developer familiar with the codebase

What NOT to Include

  • Detailed test plans
  • Exhaustive acceptance criteria
  • Deep technical specifications
  • Code examples (unless absolutely necessary for clarity)

When to Use This Skill

  • Creating new feature requests
  • Reporting bugs and issues
  • Documenting technical debt
  • Planning work items for the MCPSpy project

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.