How do I install the Hashiiiii Issues skill?

Run npx skillmds@latest add hashiiiii/hashiiiii-issues 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.

What does the Hashiiiii Issues skill do?

Use this skill to create or edit GitHub issues with a consistent body structure. It is listed under Coding & Dev Tools on SkillMD.

Is Hashiiiii Issues 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 Hashiiiii Issues?

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 Hashiiiii Issues free to use?

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

Who published Hashiiiii Issues?

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

Hashiiiii Issues by hashiiiii — Agent Skill

Name: Hashiiiii Issues
Author: hashiiiii

File contents

Issue Conventions

Use the same headings and order in every issue body.

Locale

Before you draft an issue, resolve its language:

If project instructions specify an issue language, use that language.
If project instructions do not specify a language, use the resolved issues key from the context.
If the context has no resolved keys, read the first existing locale file.
Use this file order: local, project, user, and bundled LOCALE.default.md.
Use <absolute-git-dir>/rules-for-ai/LOCALE.md for the local file.
Use <repo>/.rules-for-ai/LOCALE.md for the project file.
Use ${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md for the user file.
If no locale file exists, use en_US.
Use the issues language for the issue title and body.

Always write the section headings in English. Do not change the template structure.

If issues is ja_JP, keep the English headings. Write the text below each heading in Japanese.

When to Use

Before gh issue create
Before you edit an issue body
If the user asks you to draft an issue

Issue Body Template

Use these exact headings in this order:

## Background

## Problem

## Scope

### In scope

### Out of scope

## Design

## Acceptance criteria

## Notes

Section Guide

Section	Purpose
Background	Explain the context, reason, and earlier decisions.
Problem	Describe current defects or missing behavior.
Scope / In scope	List the required deliverables.
Scope / Out of scope	List the excluded items.
Design	Describe the method, alternatives, and important decisions.
Acceptance criteria	Give an objective checklist for approval or closure.
Notes	Add links, dependencies, open questions, and later work.

Use - [ ] checkboxes in Acceptance criteria. Each item must have an objective result.

Creating an Issue

gh issue create --title "<title>" --body "$(cat <<'EOF'
## Background

## Problem

## Scope

### In scope

### Out of scope

## Design

## Acceptance criteria

- [ ]

## Notes

EOF
)"

Common Mistakes

Mistake	Fix
Missing Out of scope	Always list the excluded items.
Vague Acceptance criteria	Use checkboxes with objective results.
Design information in Problem	Put the current state in Problem. Put the solution in Design.
Missing Background	Explain the reason for the work before the problem.

---name: hashiiiii-issuesdescription: Use this skill to create or edit GitHub issues with a consistent body structure.---# Issue ConventionsUse the same headings and order in every issue body.## LocaleBefore you draft an issue, resolve its language:1. If project instructions specify an issue language, use that language.2. If project instructions do not specify a language, use the resolved `issues` key from the context.3. If the context has no resolved keys, read the first existing locale file.4. Use this file order: local, project, user, and bundled `LOCALE.default.md`.5. Use `<absolute-git-dir>/rules-for-ai/LOCALE.md` for the local file.6. Use `<repo>/.rules-for-ai/LOCALE.md` for the project file.7. Use `${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md` for the user file.8. If no locale file exists, use `en_US`.9. Use the `issues` language for the issue title and body.Always write the section headings in English. Do not change the template structure.If `issues` is `ja_JP`, keep the English headings. Write the text below each heading in Japanese.## When to Use- Before `gh issue create`- Before you edit an issue body- If the user asks you to draft an issue## Issue Body TemplateUse these exact headings in this order:```markdown## Background## Problem## Scope### In scope### Out of scope## Design## Acceptance criteria## Notes```## Section Guide| Section | Purpose ||---------|---------|| Background | Explain the context, reason, and earlier decisions. || Problem | Describe current defects or missing behavior. || Scope / In scope | List the required deliverables. || Scope / Out of scope | List the excluded items. || Design | Describe the method, alternatives, and important decisions. || Acceptance criteria | Give an objective checklist for approval or closure. || Notes | Add links, dependencies, open questions, and later work. |Use `- [ ]` checkboxes in `Acceptance criteria`. Each item must have an objective result.## Creating an Issue```bashgh issue create --title "<title>" --body "$(cat <<'EOF'## Background## Problem## Scope### In scope### Out of scope## Design## Acceptance criteria- [ ]## NotesEOF)"```## Common Mistakes| Mistake | Fix ||---------|-----|| Missing Out of scope | Always list the excluded items. || Vague Acceptance criteria | Use checkboxes with objective results. || Design information in Problem | Put the current state in Problem. Put the solution in Design. || Missing Background | Explain the reason for the work before the problem. |

Frequently asked questions

Hashiiiii Issues