agentleFS
hashiiiiihashiiiii/rules-for-ai/skills/hashiiiii-issues/SKILL.md

hashiiiii-issues

Skill10 starsChanged 3 months agoMITView on GitHub

Use this skill to create or edit GitHub issues with a consistent body structure.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Create an issue with gh issue create --title "<title>" --body-file <file>.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Issue Conventions

Resolve the issues language through the shared locale rules for the title and body. Keep headings in English and use this structure in this order:

## Background

## Problem

## Scope

### In scope

### Out of scope

## Design

## Acceptance criteria

## Notes

Use Background for the context, reason, and earlier decisions. Describe current defects or missing behavior in Problem. List deliverables and exclusions under In scope and Out of scope; explain the approach and key decisions under Design; and put links, dependencies, or open questions in Notes. Make Acceptance criteria objective - [ ] items.

Create an issue with gh issue create --title "<title>" --body-file <file>.

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.