report-issue
From the author
Дефект или пожелание - в репозиторий набора скилов или плагина AI-EDT. Используй когда скрипт скила падает или дает неверный результат, правило расходится с поведением платформы или плагина, инструмент AI-EDT работает не так, как описан, либо пользователь просит сообщить разработчикам, завести issue, отправить баг или пожелание
Install
npx skills add Desko77/claude-code-skills-1c --skill report-issue -a claude-code
Installs to .claude/skills/report-issue/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ai-issue-reportarcasilesgroup/ai-engineeringReports 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.Security★ 62
- scenario-reportscenario-labs/skillsUse when a Scenario user wants to report a bug or request a change, on the public tracker at github.com/scenario-labs/skills or by email to [email protected]: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with diagnostics_run, stripping keys, signed asset URLs, and personal data, asking before sharing a team or project id, or building a prefilled issue URL. Keywords: file an issue, feature request, feedback.Productivity★ 1.5K
- propose-issueOutlineDriven/outline-driven-developmentUse when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.Other★ 56
- debug-live-issuehoangsonww/Claude-Code-Agent-MonitorDebug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.Engineering★ 1.1K
- dev-retrocodeaholicguy/ai-devkitAI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, post-mortem, or "what went wrong", or when another skill offers one after a feature or fix.Other★ 1.7K
- cherry-studio-feedbackCherryHQ/cherry-studioUse when Cherry Studio 用户希望报告、提交或整理 BUG、UI/UX 问题或功能建议，但未明确要求创建 GitHub Issue。Design★ 53.2K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in