What is create-bug-report-issue?

A guided command for writing a bug report that follows the repository's GitHub issue template. It collects the problem, reproduction steps, expected and actual results, and environment details.

It is for creating a complete, structured GitHub bug issue from repository templates.

It helps prevent missing information that makes a software defect hard to understand or reproduce.

How felipebarcelospro/igniter-js configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to felipebarcelospro/igniter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/felipebarcelospro/igniter-js/main/.github/prompts/create-bug-report-issue.md

Clone the repo

git clone --depth 1 https://github.com/felipebarcelospro/igniter-js

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-bug-report-issue/github.svg)](https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-bug-report-issue)

Your own site

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-bug-report-issue"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-bug-report-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/felipebarcelospro/igniter-js/create-bug-report-issue"><img src="https://agentmods.dev/badge/commands/felipebarcelospro/igniter-js/create-bug-report-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 689 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00689
Opus 5.5	$0.00000	$0.00276
Sonnet 5.5	$0.00000	$0.00138
Haiku 4.5	$0.00000	$0.00069

Measured 1mo ago against content hash 03d453faf787, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-bug-report-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/create-bug-report-issue.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prompt: Create a Bug Report Issue (Using Repository Templates)

Purpose

Guide the creation of a complete, high-quality bug report aligned with this repository's issue templates. Collect all required details, validate clarity and reproducibility, then generate a well-structured GitHub issue body that matches the template fields.

Prerequisites

Confirm the repository contains issue templates under .github/ISSUE_TEMPLATE/.
Prefer the template named bug_report or equivalent; mirror its sections and required fields.

Step-by-Step Instructions

Gather Problem Context
- Ask the user for a concise title that captures the defect.
- Ask for a clear description summarizing the problem and impact.
- Request repository path(s) or package scope(s) impacted (e.g., core, cli, adapter-redis, apps/www, repo).
Reproduction
- Collect exact reproduction steps as a numbered list (minimal steps preferred).
- Request expected behavior versus actual behavior.
- Ask for reproduction repository/branch or a code snippet if available.
Environment Details
- Ask for environment info such as:
  - OS and version (e.g., macOS 14.x)
  - Node.js/Bun/Deno versions where applicable
  - Package manager and version (npm/pnpm/bun)
  - Igniter.js package versions (if applicable)
  - Any relevant env vars, feature flags, or configuration toggles
Logs and Evidence
- Ask for stack traces, console logs, screenshots, or network traces.
- If test failures are involved, request the exact failing test name/output.
Impact & Severity
- Ask the user to classify severity (e.g., blocker/critical/major/minor/trivial).
- Ask for frequency (always/sometimes/rarely) and scope (single package, multiple packages).
Triage Metadata
- Suggest labels/scopes based on provided paths (e.g., pkg:core, app:www, kind:bug).
- Suggest a milestone (if applicable) and link related issues/PRs.
Build Issue Body Using Template
- Construct a markdown body mirroring the repository bug report template sections:
  - Title
  - Description
  - Steps to Reproduce
  - Expected Behavior
  - Actual Behavior
  - Environment
  - Logs/Screenshots
  - Impact/Severity
  - Additional Context / Related Issues
- Ensure all sections are present; insert N/A for fields not provided.

Read the full file on GitHub · 70 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 70 lines · 0 tokens per session scan A 03d453faf787

Subscribe to this mod's changes

create-bug-report-issue is a command published in the GitHub repository felipebarcelospro/igniter-js (240 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 689 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-27.

Debugging Project management api express fastify framework http middleware

create-bug-report-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-bug-report-issuefelipebarcelospro/igniter-js	Command	240	29d ago	Apache-2.0	A	0	GitHub Copilot
replayhoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	17	Claude Code
doctorhoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	11	Claude Code
tail-eventshoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	17	Claude Code
healthhoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	18	Claude Code
slohoangsonww/Claude-Code-Agent-Monitor	Command	1.1k	yesterday	MIT	A	17	Claude Code
editor-lifecycle-and-observabilityAlex-Rachel/TEngine	Command	2.4k	15d ago	MIT	A	0	Claude Code

igniter-js: Command for GitHub Copilot