issue-format

Standardize GitHub issue titles and descriptions using a strict frontmatter template.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bitsocialnet/bitsocial-web --skill issue-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-format
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/issue-format
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill issue-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formats GitHub issue titles and descriptions to facilitate tracking problems that were fixed. This keeps issues consistent and actionable for teams.

Core Features & Use Cases

  • Template enforcement: ensures the issue title and body follow a standard structure.
  • Consistent formatting: promotes uniformity across issues, making it easier to search and triage.
  • Use Case: when proposing or implementing code changes, or when a user asks for issue suggestions.

Quick Start

Format an issue by following the template to describe the problem, its scope, and any relevant references.

Frequently Asked Questions about issue-format

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

FAQPage Schema
How do I standardize GitHub issue titles and descriptions for better traceability?

You standardize GitHub issue formatting by applying a strict frontmatter and template structure to titles and descriptions. This enforces consistent documentation across bug reports, feature requests, and proposals for predictable tracking.

What is the best way to format GitHub issues for consistent triage across codebases?

The best way to format GitHub issues for triage is using template enforcement that standardizes the title and body structure. This promotes uniformity across codebases, making issues easier to search and act on.

When do I need to use a strict markdown template for GitHub issue formatting?

You need a strict markdown template for GitHub issue formatting when proposing or implementing code changes. It ensures the issue describes the problem, its scope, and relevant references in a predictable structure.

Can I apply a standard issue format to both bug reports and feature requests?

Yes, you can apply a standard issue format to both bug reports and feature requests. The template enforces a uniform structure for describing the problem and scope across all issue types within your codebases.

Does issue formatting with frontmatter limit how I describe a problem's scope?

Issue formatting with frontmatter standardizes the structure but does not limit the content. It enforces a predictable template for the title and description, ensuring the problem, scope, and references are safely formatted and documented.