knowledge-issue-report

Generates and validates GitCode issue submission materials for cannbot-knowledge knowledge base feedback.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill knowledge-issue-report-wangwindow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-issue-report
Source: https://github.com/WangWindow/CANN-BatchMatMulMaxsum/tree/main/.agents/skills/knowledge-issue-report
Command: npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill knowledge-issue-report-wangwindow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users encounter errors in the cannbot-knowledge knowledge base—such as incorrect content, retrieval failures, graph errors, or downstream agent issues—they often submit incomplete bug reports that cannot be acted upon. This Skill structures user feedback into complete, reproducible GitCode issue submissions with all required evidence. ## Core Features & Use Cases - Structured Issue Generation: Produces a complete 16-section issue template covering problem type, versions, environment, prompts, commands, terminal output, reproduction rate, and evidence. - Material Validation: Checks 14 required materials and outputs a needs-info list when critical items like version commits, full terminal logs, or reproduction records are missing. - Reproduction Package Assembly: Defines a standardized attachment archive structure (environment.txt, command.txt, prompt.txt, terminal.log, sessions/, reproduction runs) for triage-ready submissions. - Use Case: A user finds that a knowledge query returns wrong results for an Ascend operator. The Skill collects the knowledge base commit, CLI version, verbatim query, three reproduction runs, and affected doc-id, then outputs a ready-to-file issue plus a packaged evidence archive. ## Quick Start Help me file a knowledge base issue: the knowledge-query search for 'A5 LayerNorm UB reuse' returns an incorrect document, and here are my command, terminal output, and repo commit.

Frequently Asked Questions about knowledge-issue-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report an error in the cannbot-knowledge knowledge base?

Use this Skill to structure your report. It collects the issue type, knowledge base and plugin versions, environment details, verbatim prompt and command, full terminal output, and evidence, then generates a complete GitCode issue body and attachment package.

What materials are required for a knowledge base issue report?

Fourteen items are required, including problem type, knowledge base commit, cannbot-skills version, CLI and Python versions, model identifier, verbatim prompt, full command, effective configs, run records, complete terminal output, reproduction rate, affected knowledge doc-id, expected versus actual behavior, and evidence.

How many times must I reproduce a retrieval or agent issue?

Tool, retrieval, and agent problems require at least three reproduction runs, reported as 'ran y times, occurred x times'. Stable knowledge content errors do not need repeated runs but must include the affected card and supporting evidence.

What happens if my issue report is missing materials?

The Skill outputs a needs-info checklist identifying the missing items instead of a full issue. Issues lacking critical materials are marked needs-info and deprioritized until complete, reproducible evidence is provided.

Can I redact sensitive information from configs and logs?

Yes, sensitive values may be redacted, but the configuration structure must be preserved. Prompts, commands, and terminal output must remain verbatim and complete; selective excerpts or truncated logs are not accepted.