New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bug Reporting Excellence

by proffesor-for-testing in proffesor-for-testing/agentic-qe

Write high-quality bug reports that get fixed quickly. An agent skill from proffesor-for-testing/agentic-qe.

MITAuto-check passedTesting & QA

Install Bug Reporting Excellence

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe bug-reporting-excellence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/bug-reporting-excellence .claude/skills/bug-reporting-excellence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bug-reporting-excellence
GitHub stars
495
Token cost
~1.7k tokens
SKILL.md length
371 words
Files
3 (incl. scripts)
Skills in repo
93
Repo updated
First seen
Licence
MIT

At a glance

Write high-quality bug reports that get fixed quickly. An agent skill from proffesor-for-testing/agentic-qe.

  • Works in 5 steps: TITLE: [Component] fails [Condition]… → DESCRIBE: Expected behavior → Actual… → INCLUDE: Environment, severity,… → …
  • Training teams on bug reporting
  • SKILL.md covers Quick Reference Card, Essential Information, Example: Excellent Bug Report and Anti-Patterns, plus 6 more sections
  • Establishing bug report standards

What it does

Bug Reporting Excellence is an agent skill from proffesor-for-testing/agentic-qe. Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `schemas/output.json` and `scripts/validate-config.json`).

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Training teams on bug reporting
  • Establishing bug report standards

Example prompts

  • “/bug-reporting-excellence”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. TITLE: [Component] fails [Condition] causing [Impact]
  2. DESCRIBE: Expected behavior → Actual behavior → Steps to reproduce
  3. INCLUDE: Environment, severity, screenshots/logs, business impact
  4. ISOLATE: Narrow down conditions (browser, user, amount thresholds)
  5. ONE BUG = ONE REPORT (don't combine issues)

What it can do on your machine

Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bug Reporting Excellence loads about 1.7k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 371 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 371 words, ~1,713 tokens.

Download SKILL.mdSave it as .claude/skills/bug-reporting-excellence/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
bug-reporting-excellence
description
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
category
quality-communication
priority
high
tokenEstimate
900
agents
qe-quality-analyzer, qe-production-intelligence, qe-flaky-test-hunter
implementation_status
optimized
optimization_version
1
last_optimized
2025-12-03
quick_reference_card
true
tags
bugs, reporting, communication, triage, quality
trust_tier
2

Bug Reporting Excellence

<default_to_action> When reporting bugs:

  1. TITLE: [Component] fails [Condition] causing [Impact]
  2. DESCRIBE: Expected behavior → Actual behavior → Steps to reproduce
  3. INCLUDE: Environment, severity, screenshots/logs, business impact
  4. ISOLATE: Narrow down conditions (browser, user, amount thresholds)
  5. ONE BUG = ONE REPORT (don't combine issues)

Bug Report Formula:

markdown
## [Component] Issue Title
**Severity:** Critical/High/Medium/Low
**Environment:** Production/Staging/Dev

### Expected Behavior
What should happen

### Actual Behavior
What actually happens (with error messages)

### Steps to Reproduce
1. Step one
2. Step two
3. Observe issue

### Impact
How this affects users/business

Critical Success Factors:

  • Reproducible steps (100%)
  • Environment info (100%)
  • Business impact stated (90%)
  • Screenshots or logs (80%) </default_to_action>

Quick Reference Card

Severity Levels
LevelDefinitionExamples
CriticalSystem down, data loss, securityDB deleted, payments broken, credentials exposed
HighMajor feature broken, many usersCan't checkout, search broken, dashboard fails
MediumPartial break, workaround existsFilter broken (refresh works), slow export
LowCosmetic, rare edge caseButton wraps on mobile, tooltip wrong color
Title Formula

❌ Bad: "Checkout broken" ✅ Good: "Payment fails with Visa cards when order total > $1000"

Pattern: [Component] fails [Condition] causing [Impact]

Essential Information

Environment Details
Browser: Chrome 120.0.6099.109 (Windows)
OS: Windows 11 Pro
URL: https://example.com/checkout
Date/Time: 2025-10-17 14:23 UTC
User: test@example.com (ID: 12345)
Request ID: abc-123-def-456
Supporting Evidence

Error Messages:

json
{
  "error": "Payment service unavailable",
  "code": "GATEWAY_TIMEOUT",
  "requestId": "abc-123-def-456"
}

Console Logs:

[ERROR] PaymentGateway: Connection timeout after 30000ms
  at PaymentGateway.charge (gateway.js:145)

Example: Excellent Bug Report

markdown
## [Checkout] Payment processing times out for orders > $1000

**Severity:** High
**Environment:** Production
**Affected Users:** ~15% of premium purchases

### Expected Behavior
Payment completes within 5 seconds regardless of amount.

### Actual Behavior
For orders above $1000, payment gateway times out after 30 seconds.
User sees "Payment failed" error. Order not created.

### Steps to Reproduce
1. Add items totaling $1,050 to cart
2. Proceed to checkout
3. Enter payment: Visa 4532 1234 5678 9010
4. Click "Place Order"
5. Wait 30+ seconds
6. Observe timeout error

### Environment
- Browser: Chrome 120 (Windows 11)
- User: test@example.com
- Request ID: abc-123-def-456

### Evidence
Console error: `PaymentGateway timeout: 30000ms exceeded`
Network: /api/checkout: 30.14s (timeout)

### Impact
- Lost revenue: ~$15K/week from failed orders
- 23 support tickets this week
- Affects 15% of orders over $1000

### Additional Context
Started after Oct 15 deployment (v2.3.0)
Possibly related to PR #456 (fraud check)

Anti-Patterns

❌ BadProblem✅ Good
"Checkout is broken"What doesn't work?"Payment button doesn't respond when clicked"
"I saw an error"No reproduction stepsFull steps with conditions
"Page loads slowly"No specifics"Dashboard takes 12s to load (should be <3s)"
Multiple bugs in oneCan't track separatelyOne report per bug

Agent Integration

typescript
// Automated bug triage
const triage = await Task("Triage Bug", {
  title: 'Payment fails for orders > $1000',
  description: bugDescription,
  steps: reproductionSteps
}, "qe-quality-analyzer");

// Returns: { severity, priority, component, suggestedAssignee, relatedIssues }

// Duplicate detection
const dupeCheck = await Task("Check Duplicates", {
  bugReport: newBug,
  similarityThreshold: 0.85
}, "qe-quality-analyzer");

// Bug report enhancement
const enhanced = await Task("Enhance Report", {
  originalReport: userSubmittedBug,
  addMissingInfo: true,
  identifyRootCause: true
}, "qe-production-intelligence");

Agent Coordination Hints

Memory Namespace
aqe/bug-reports/
├── triaged/*          - Bug triage results
├── duplicates/*       - Duplicate detection
├── patterns/*         - Recurring bug patterns
└── root-cause/*       - Root cause analyses
Fleet Coordination
typescript
const bugFleet = await FleetManager.coordinate({
  strategy: 'bug-investigation',
  agents: [
    'qe-quality-analyzer',        // Triage and categorize
    'qe-flaky-test-hunter',       // Check if test-related
    'qe-production-intelligence'  // Check production logs
  ],
  topology: 'parallel'
});
Show full SKILL.md (153 more words)Show less

Remember

Your bug report is the starting point for someone else's work. Make it complete (all info needed), clear (anyone can follow), concise (no noise), and actionable (developer knows next step).

Good bug reports = Faster fixes = Better product = Happier users

Skill Composition

  • After finding bug → Start with /test-failure-investigator for root cause
  • Prevent regression → Use /regression-testing to add test preventing recurrence
  • Track quality → Feed into /test-metrics-dashboard for trend analysis

Gotchas

  • Agent omits environment details (OS, browser version, node version) — these are critical for reproduction
  • "Steps to reproduce" that start with "1. Open the app" are useless — specify exact URL, user role, and state
  • Agent combines multiple bugs into one report — enforce ONE BUG = ONE REPORT strictly
  • Screenshots without annotations don't help — always highlight the actual error area
  • Severity assessment is often wrong — agent marks everything as "critical" or everything as "low"

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in assets/skills/bug-reporting-excellence of proffesor-for-testing/agentic-qe.

  • SKILL.md
  • schemas/output.json
  • scripts/validate-config.json

Open the folder on GitHubat commit 829d030

Compare with similar skills

Bug Reporting Excellence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bug Reporting Excellence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Reporting Excellence this skillproffesor-for-testing/agentic-qe495—~1.7kAutomated safety check: PassMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Moav E2EMotherofallVPNs/MoaV448—~1.9kAutomated safety check: NotesMIT
Creating A Coral TaskHuman-Agent-Society/CORAL1.1k—~2.2kAutomated safety check: PassApache-2.0
Launch Rlmarin-community/marin3.9k—~894Automated safety check: PassApache-2.0

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed

  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes

  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Launch Rl

    marin-community/marin

    Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.

    3.9k GitHub stars~894 tokensUpdated today
    Testing & QAAuto-check passed

  • Actionbook Web Test

    actionbook/actionbook

    Run browser-based web tests against websites using Actionbook CLI.

    1.6k GitHub stars~9.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from proffesor-for-testing/agentic-qe

All 93 skills in this repo

  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    495 GitHub stars~1.8k tokensUpdated 5 days ago
    Auto-check passed

  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    495 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed

  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    495 GitHub stars~2.4k tokensUpdated 5 days ago
    Auto-check passed

  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    495 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    495 GitHub stars~2.7k tokensUpdated 5 days ago
    Auto-check: notes

  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    495 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Bug Reporting Excellence

What does Bug Reporting Excellence do?

Write high-quality bug reports that get fixed quickly. An agent skill from proffesor-for-testing/agentic-qe. Bug Reporting Excellence is an agent skill from proffesor-for-testing/agentic-qe. Write high-quality bug reports that get fixed quickly.

When should I use Bug Reporting Excellence?

Bug Reporting Excellence fits situations like: training teams on bug reporting; establishing bug report standards.

How do I install Bug Reporting Excellence in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -a claude-code`. Or copy the skill folder (assets/skills/bug-reporting-excellence in proffesor-for-testing/agentic-qe) into .claude/skills/bug-reporting-excellence in your project. Claude Code loads it when a task matches its description.

How do I install Bug Reporting Excellence in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -a codex`. Or copy the skill folder (assets/skills/bug-reporting-excellence in proffesor-for-testing/agentic-qe) into .agents/skills/bug-reporting-excellence in your project. Codex loads it when a task matches its description.

Can I use Bug Reporting Excellence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-reporting-excellence, .gemini/skills/bug-reporting-excellence, .github/skills/bug-reporting-excellence and .opencode/skills/bug-reporting-excellence in your project.

What does Bug Reporting Excellence need to run?

SKILL.md names no scripts, command-line tools or credentials: Bug Reporting Excellence is instructions for the agent only.

Does Bug Reporting Excellence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Bug Reporting Excellence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Bug Reporting Excellence use?

Bug Reporting Excellence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bug Reporting Excellence use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bug Reporting Excellence?

Skills that share tags, products or a category with Bug Reporting Excellence: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 448 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Reporting Excellence?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 495 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 4, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.