reporting-issues
/reporting-issues
Use this skill when you need to report on a troubleshooting session — turn raw debugging notes into a clear, reproducible troubleshooting report.
- Author
- jiaxiaojunQAQ ↗
- Repository
- SkillCamo ↗
- Licence
- Apache-2.0
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use this skill when you need to report on a troubleshooting session — turn raw debugging notes into a clear, reproducible troubleshooting report.
Original author description
Use this skill when you need to report on a troubleshooting session — turn raw debugging notes into a clear, reproducible troubleshooting report.
How it works
- Workflow
- Report Template
- Quality bar
SKILL.md preview
--- name: reporting-issues description: Use this skill when you need to report on a troubleshooting session — turn raw debugging notes into a clear, reproducible troubleshooting report. --- # Instructions Turn a troubleshooting/debugging session into a structured, reproducible report. Prefer the `@troubleshoot-report-generator` agent when it is available; otherwise produce the report yourself by following the workflow below. ## Workflow 1. **Gather context** — collect what was observed: the symptom, when it started, the affected component/environment, and any error output or logs. Ask only for genuinely missing facts. 2. **Establish reproduction** — write the minimal, ordered steps that reproduce the issue, plus the expected vs. actual result. If it is intermittent, state the observed frequency. 3. **Diagnose** — record what was checked, what was ruled out, and the evidence that points to the root cause. Separate confirmed facts from hypotheses. 4. **Resolve** — describe the fix or workaround applied, and how it was verified to work. 5. **Follow up** — list residual risks, monitoring to add, and any preventive action. ## Report Template ```markdown # Troubleshooting Report: <short title> - **Severity:** Critical | High | Medium | Low - **Status:** Resolved | Mitigated | Open - **Component / Environment:** <service, version, OS, region> - **Reported / Resolved:** <timestamps> ## 1. Summary <one paragraph: what broke, impact, current state> ## 2. Reproduction Steps: 1. ... - **Expected:** ... - **Actual:** ... - **Frequency:** always | intermittent (~X%) ## 3. Diagnosis - Checked: ... - Ruled out: ... - **Root cause:** ... ## 4. Resolution - Fix / workaround: ... - Verification: ... ## 5. Follow-up - Residual risk: ... - Monitoring / prevention: ... ``` ## Quality bar - Every claim is backed by an observation (log line, command output, metric) — no speculation in the root-cause section. - The reproduction section is sufficient for someone else to trigger the issue unaided. - The report is skimmable: a reader gets impact and root cause from the Summary alone.
Versions
The database has no other skills named reporting-issues.
Database snapshot: 13.11.2026 · package version c9660f3185d9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90reporting-bugs
Transforms rough tester notes, screenshots, console output, or observed behavior into reproducible defect reports with severity, evidence, and follow-up guidance. Use when logging bugs, triaging intermittent issues, or rewriting vague defect notes into developer-ready reports. - 90bb-report-writing
Use when a bb tool returned something wrong or misleading and a reproducible report is needed — the optional agent-report form with version, doctor, call, freshness and expected vs actual. - 100debug-systematic
Apply a systematic four-phase debugging workflow when the user asks to debug an issue, investigate a bug, troubleshoot a problem, or find the root cause of unexpected behavior - 90to-project
Use when the user wants to turn an idea, a notes dump, or a session transcript into a complete agent-ready local project, or to fold new input into a project that already exists. Triggers include "turn this into a project", "scaffold a project from this", "make a project out of… - 100customerio-advanced-troubleshooting
Apply Customer.io advanced debugging techniques. Use when diagnosing complex issues, investigating delivery problems, or debugging integration failures. Trigger with phrases like "debug customer.io", "customer.io investigation", "customer.io troubleshoot", "customer.io incident". - 90discussion-refine
Turn a rough design discussion into a structured written brief. Use when the user has unstructured notes, chat logs, or conversation fragments that need to become a clear document with positions, open questions, and decision points.