reporting-issues
Create troubleshooting session reports
Transform debugging sessions into structured, shareable reports. This skill helps document issues, solutions, and findings for team knowledge sharing and future reference.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「reporting-issues」。 Use @reporting-issues to document this session where I fixed the database connection timeout issue by increasing the pool size.
預期結果:
- ## Troubleshooting Report
- ### Issue Summary
- Database connection timeouts occurring under load
- ### Root Cause
- Connection pool size was too small for concurrent requests
- ### Resolution
- Increased pool size from 10 to 50 connections
- ### Verification
- Tested with 100 concurrent users, no timeouts observed
安全審計
安全Static analysis detected a false positive pattern match for 'Weak cryptographic algorithm' at SKILL.md:3. Manual review confirms this is benign YAML frontmatter describing the skill's purpose. No cryptographic code, algorithms, or security-sensitive patterns exist in the skill files. The skill is a simple documentation wrapper that references another agent for report generation.
品質評分
你能建構什麼
Document customer support issues
Transform support ticket conversations into structured reports that capture the full problem history, troubleshooting steps taken, and final resolution for knowledge base entries.
Create sprint retrospective reports
After incident response sessions, generate reports summarizing what went wrong, how it was fixed, and preventive measures for team retrospectives and process improvement.
Build personal debugging logs
Keep a personal log of complex debugging sessions with clear documentation of the problem, investigation steps, and solution for future reference when similar issues arise.
試試這些提示
Use the @reporting-issues skill to create a troubleshooting report from this debugging session: [Describe the issue, steps taken, and outcome]
Generate a comprehensive troubleshooting report using @reporting-issues. Include: - Initial problem description - All debugging steps performed - Key findings and observations - Final resolution - Recommendations for prevention
Create a troubleshooting report with @reporting-issues formatted for a knowledge base. Make it reproducible by including exact commands used and environment details.
Use @reporting-issues to document this debugging session for handoff to another team. Include context, current status, and next steps.
最佳實務
- Include specific error messages and timestamps when describing issues
- Document both what was tried and why it did not work
- Add environmental context like versions, configs, and system details
避免
- Skipping the root cause analysis and only documenting the fix
- Using vague descriptions like it broke or it did not work
- Failing to verify the fix before closing the session