generate-github-bug-report

Stars13

Forks5

UpdatedMarch 20, 2026 at 20:42

Use when generating a high-quality GitHub bug report following the repository's specific templates and standards.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

gethnet

gethnet/litellm-connector-copilot

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	generate-github-bug-report
description	Use when generating a high-quality GitHub bug report following the repository's specific templates and standards.

Generate GitHub Bug Report

Use this skill to create well-structured, detailed, and actionable bug reports that adhere to the repository's .github/ISSUE_TEMPLATE/bug_report.yml (or similar) requirements.

Outcome

A complete, Markdown-formatted bug report (or YAML-aligned text) ready to be pasted into a GitHub issue, containing all necessary reproduction steps, environment details, and logs.

Workflow

1. Gather Context

Identify the core issue: What is broken? What was the user trying to do?
Collect environment details:
- AI/LLM Provider (OpenAI, Anthropic, etc.)
- AI/LLM Model name (gpt-4o, claude-3-5-sonnet, etc.)
- VS Code version and Extension version.
Locate error logs: Check the "LiteLLM" output channel or VS Code Developer Tools (Console).

2. Formulate Reproduction Steps

Create a clear, numbered list of steps.
Start from a neutral state (e.g., "Open VS Code").
Be specific about inputs or configurations used.

3. Define Expectations

Contrast "What happened" (Actual) with "What should have happened" (Expected).

4. Apply Template Structure

Follow the structure defined in .github/ISSUE_TEMPLATE/bug_report.yml:

Title: Prefix with [Bug]: followed by a concise summary.
Description: Clear summary of the bug.
Steps to Reproduce: Numbered list.
Expected Behavior: What you wanted to see.
Environment & LLM Details:
- Provider: Specify the backend.
- Model: Specific model string.
Error Output/Log: Wrap logs in ```shell blocks.
Additional Context: Screenshots, related issues, or specific workspace settings.

Quality Criteria

Actionable: A maintainer should be able to follow the steps and see the bug.
Complete: No missing mandatory fields (Provider, Model, Logs).
Clean: Proper Markdown formatting, no unnecessary "noise" or conversational filler.

Example Prompt to Invoke

"I'm getting a 401 error when trying to use the completions provider with my local LiteLLM proxy. Can you generate a bug report for me?"

More from this repository

same repository

plan-metadata-management

gethnet/litellm-connector-copilot

Use when creating, reviewing, repairing, or updating YAML frontmatter metadata for implementation plans in .plans/. Covers plan lifecycle status, archive records, GitHub traceability, implementation commits, release versions, validation results, and schema compliance.

2026-07-1713

posthog-integration

gethnet/litellm-connector-copilot

PostHog API / Integration for NodeJS/Typescript. Use when: implementing PostHog telemetry, adding analytics events, configuring PostHog adapters, writing telemetry tests, integrating feature flags, uploading sourcemaps, or debugging PostHog capture issues.

2026-04-1913

ts-no-any

gethnet/litellm-connector-copilot

Use when implementing or refactoring TypeScript code to ensure strict type safety and avoid the 'any' type. Provides strategies for unknown types, generics, and type guards.

2026-03-2013

vscode-extension-implementation

gethnet/litellm-connector-copilot

Use when implementing or refactoring VS Code extension features in this repository with a TDD-first workflow, modular architecture, and full validation.

2026-03-0813

vscode-extension-investigation

gethnet/litellm-connector-copilot

Use when validating VS Code extension behavior, implementation, tests, or architecture before coding changes in this repository.

2026-03-0813

Generate GitHub Bug Report

Use this skill to create well-structured, detailed, and actionable bug reports that adhere to the repository's .github/ISSUE_TEMPLATE/bug_report.yml (or similar) requirements.

Outcome

A complete, Markdown-formatted bug report (or YAML-aligned text) ready to be pasted into a GitHub issue, containing all necessary reproduction steps, environment details, and logs.

Workflow

1. Gather Context

Identify the core issue: What is broken? What was the user trying to do?

Collect environment details:

AI/LLM Provider (OpenAI, Anthropic, etc.)
AI/LLM Model name (gpt-4o, claude-3-5-sonnet, etc.)
VS Code version and Extension version.

Locate error logs: Check the "LiteLLM" output channel or VS Code Developer Tools (Console).

2. Formulate Reproduction Steps

Create a clear, numbered list of steps.

Start from a neutral state (e.g., "Open VS Code").

Be specific about inputs or configurations used.

3. Define Expectations

Contrast "What happened" (Actual) with "What should have happened" (Expected).

4. Apply Template Structure

Follow the structure defined in .github/ISSUE_TEMPLATE/bug_report.yml:

Title: Prefix with [Bug]: followed by a concise summary.

Description: Clear summary of the bug.

Steps to Reproduce: Numbered list.

Expected Behavior: What you wanted to see.

Environment & LLM Details:

Provider: Specify the backend.
Model: Specific model string.

Error Output/Log: Wrap logs in ```shell blocks.

Additional Context: Screenshots, related issues, or specific workspace settings.

Quality Criteria

Actionable: A maintainer should be able to follow the steps and see the bug.

Complete: No missing mandatory fields (Provider, Model, Logs).

Clean: Proper Markdown formatting, no unnecessary "noise" or conversational filler.

Example Prompt to Invoke

"I'm getting a 401 error when trying to use the completions provider with my local LiteLLM proxy. Can you generate a bug report for me?"