ai-issue-report
De la autor
Reports a reproducible fault to a team or an upstream project — for ai-engineering itself or for any service the client is building — as a governed payload: closed allow-listed fields, scanned for machine paths, personal data (PII) and secrets before anything is written, draft kept local, and the exact bytes shown with their SHA-256 before anybody confirms anything. Trigger for "report this bug", "file an issue", "the framework is broken", "send this upstream", "write the incident report". Not for a fault in your own code that still needs a diagnosis — use /ai-debug first. Not for a vulnerability sent anywhere public: that routes to private disclosure, and this skill refuses the other way.
Instalare
npx skills add arcasilesgroup/ai-engineering --skill ai-issue-report -a claude-code
Se instalează în .claude/skills/ai-issue-report/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 82
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- ai-debugarcasilesgroup/ai-engineeringFinds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-verify. Not for exploring an unfamiliar area — use /ai-explore. Not for designing the fix — once the cause is named, use /ai-orchestrator. Not for reporting the fault to outsiders — use /ai-issue-report.Inginerie★ 62
- bug-reportmohitagw15856/pm-claude-skillsWrite a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.Redactare★ 1.5K
- report-issuemicrosoft/power-platform-skillsUse when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.Productivitate★ 1.1K
- filing-bug-reportsmatlab/simulink-agentic-toolkitGenerate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.Finanțe★ 1.3K
- security-reviewgithub/awesome-copilotAI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.Securitate★ 40.7K
- bug-reportingmgifford/accessibility-skillsLoad this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.Testare★ 57
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te