reporting-issues

Generates structured markdown issue reports for bugs, feature requests, and other issue types.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill reporting-issues-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting-issues
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/reporting-issues
Command: npx skills add https://github.com/falentio/cimi --skill reporting-issues-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague issue reports force maintainers into repeated follow-up questions, delaying fixes or causing reporters to abandon issues entirely. This Skill produces complete, actionable issue reports with reproduction steps, environment details, and evidence so problems can be understood and resolved in one pass. ## Core Features & Use Cases - Bug Report Template: Generates reports with summary, environment, exact reproduction steps, expected versus actual behavior, evidence, regression history, severity, and workarounds. - Feature Request Template: Produces requests with motivation, proposed behavior, testable acceptance criteria, technical notes, and alternatives considered. - Specialized Issue Types: Adapts templates for security vulnerabilities, performance problems, and documentation gaps with type-specific fields. - Use Case: A user reports that file uploads fail intermittently. The Skill produces a markdown bug report specifying the file name, size, and type, exact OS and browser versions, pasted error output, and a severity rating, so a maintainer can reproduce it immediately. ## Quick Start Write a bug report for the login page returning a 500 error after entering valid credentials on Chrome.

Frequently Asked Questions about reporting-issues

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

FAQPage Schema
How do I write a good bug report that developers can reproduce?

A reproducible bug report includes exact steps from a clean state with specific inputs, full environment details (OS, browser, app version), expected versus actual behavior, and pasted error messages or logs. Add screenshots and regression info to eliminate follow-up questions.

What should a feature request include to get accepted?

A feature request needs a clear motivation with evidence of user demand, proposed end-to-end behavior, and concrete testable acceptance criteria. Include technical notes on affected components and alternatives considered to help maintainers evaluate the proposal.

How do I report a security vulnerability in an issue?

Keep reproduction steps and impact so a developer can verify the bug and confirm the fix, and add the vulnerability type with a CWE reference plus a suggested fix. Never include exploit payloads in public issues, and omit environment details for server-side flaws.

What should I do when issue report information is missing?

Mark the gap explicitly with a note describing what information is needed rather than deleting the section. An empty section signals what is missing, while a removed section hides the gap from the reporter and assignee.

When should I not use an issue report template?

Issue templates are not appropriate for code review feedback, pull request descriptions, or changelog entries, which follow different conventions. Use them only for bug reports, feature requests, and similar tracked work items.