report-bug
Report a defect of reviewer or its plugin as an anonymized GitHub issue in mimfort/rag_for_git, after explicit user approval. Use when a reviewer tool breaks its own contract, a skill prescribes an impossible step, a stated invariant fails, or the user asks to report a reviewer bug.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- report-bug
- description
- Report a defect of reviewer or its plugin as an anonymized GitHub issue in mimfort/rag_for_git, after explicit user approval. Use when a reviewer tool breaks its own contract, a skill prescribes an impossible step, a stated invariant fails, or the user asks to report a reviewer bug.
03 SKILL.md 正文
Report Bug
Reply in Russian. This channel reports defects of the tool, never problems of the user's project. The server triages, anonymizes, assembles the issue and publishes it; the skill only carries the conversation and the approval.
The plugin runs on commercial codebases. Never pre-redact by hand and never paste source code, paths, repo/branch/file names, task keys, board URLs, hosts or tokens into the arguments in the hope of "cleaning them up" — pass what you observed and let the server anonymize it. The sanitizer is deterministic Python; a model rewriting the text first only hides what it should have removed.
- Decide whether it is ours. Pick
kindfrom the tool contract, and pass it as observed — the server, not you, decides whether the channel speaks:- ours:
tool_exception,contract_violation,skill_impossible,skill_contradiction,invariant_violation,deterministic_repro; - not ours:
environment,external_service,user_code,permission,llm_behaviour. The one exception: the model misbehaved because a skill instruction was contradictory → stillllm_behaviour, but setcaused_by_skill_instruction=True(a prompt bug is our bug). Anot_reportedstatus is a normal outcome — report nothing to the user beyond a brief note.
- ours:
- Pick severity.
blocker(no workaround),degraded(workaround or manual fallback exists),contract(documentation and behaviour disagree, work continues). Offerblockeranddegradedimmediately; the server markscontractwithdefer=true— collect those and offer them as one batch at the end of the session. - Preview (never skip). Call
withoutreport_bug(kind=<kind>, summary=…, expected=…, actual=…, steps=[…], severity=<level>, tool=<mcp tool name>, skill_step=<skill and step>, error_class=<exception class>, details=…, repo=<owner/name>, branch=<branch>, client_environment={"orchestrator_model": …, "subagent_models": …, "mode": "subagent|inline", "cli": …, "cli_version": …}, scale={"clusters": N, "files": N, "findings": N, "tasks": N}, index_drift=<int or null>)confirmed. Nothing is published. Handle the status:disabled— the channel is off for this repo or deploy, say so and stop;not_reported/suppressed— stop quietly. - Show and ask. Show the returned
issue_textin full, verbatim — no summary, no abridgement — plus the target repository, theenvironment_keyslist, and theidentity_notice: the issue is published from the user's GitHub account and their username will be visible in a public repository; the alternative is to decline and open the issue by hand from the prepared markdown. Offer to trim the Environment block: any lines, or the whole block. Then ask for an explicit yes. - Publish only on an explicit yes. Repeat the same call with
confirmed=Trueand, if the user trimmed anything,environment_exclude=[…](orenvironment_include=[…]). In a headless, cron or background run there is no human to approve: passnon_interactive=True, which makes the server return afallbackmarkdown instead of publishing. Never publish autonomously in any mode.published— report the issue URL.commented— a matching open issue existed; report that a comment was added and give both URLs.fallback— publication was not possible (no token, no rights, no network, headless): relay the reason, show the markdown and thefallback_urlso the user can post it by hand. This is not a session failure — continue the work that was interrupted.
- On a refusal call
report_bug(kind=…, summary=…, decline=True)with the same arguments, so the same symptom is not offered again in this session.
Every read is fail-open, and the confirmed=True call is the only write. If the channel itself
fails, say so in one line and carry on with the original task.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.