Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

triage

Étoiles15

Forks4

Mis à jour2 juillet 2026 à 21:55

Use when the user hits an error, exception, or stack trace and the cause isn't obvious — returns RANKED root-cause hypotheses with the cheapest discriminating check for each, via debug_triage

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

byPawel

byPawel/tachibot-mcp

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	triage
description	Use when the user hits an error, exception, or stack trace and the cause isn't obvious — returns RANKED root-cause hypotheses with the cheapest discriminating check for each, via debug_triage
user-invocable	true

/triage — Ranked Bug Triage

Collect the error/stack trace verbatim into error. Never trim the trace.
Gather cheap context: repro steps and recent changes (context), runtime/versions (runtime), and the implicated source (files with line ranges around the frames, e.g. 'src/app.ts:30-60').
Call debug_triage.
Relay the ranked hypotheses with their likelihoods, then run (or offer to run) the TOP hypothesis's discriminating check — logs, a breakpoint, a one-liner — before touching any fix.
If the check kills the top hypothesis, promote the named runner-up and check that one; only implement the minimal fix once a hypothesis is CONFIRMED. Then add the locking test the tool suggested.

Requires GROK_API_KEY (or XAI_API_KEY). If the tool returns its missing-key error, relay it and suggest /setup.

Plus depuis ce dépôt

même dépôt

audit

byPawel/tachibot-mcp

Use when the user wants a security review of code or a diff — OWASP/CWE findings with severity, taint/data-flow analysis, and concrete fixes via security_review

2026-07-0515

test

byPawel/tachibot-mcp

Use when the user wants tests generated for code or a diff — enumerates edge cases and failure modes first, then emits runnable test code via testgen

2026-07-0515

prompt

byPawel/tachibot-mcp

Use when a task would benefit from a structured thinking technique but you're not sure which — recommends the right prompt technique for the intent (debug, spec, refactor, decision, design) and applies it

2026-07-0315

judge

byPawel/tachibot-mcp

Use for decisions or judgments worth multiple independent perspectives — multi-model council with parallel analysis, search grounding, and synthesis (30-60s); for a quick single-call verdict use the jury tool directly

2026-07-0215

redteam

byPawel/tachibot-mcp

Use when the user shares or finishes a plan and wants it stress-tested before execution — adversarial multi-model pre-mortem with ranked risks, mitigations, and concrete plan edits

2026-07-0215

review

byPawel/tachibot-mcp

Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict

2026-07-0215

name	triage
description	Use when the user hits an error, exception, or stack trace and the cause isn't obvious — returns RANKED root-cause hypotheses with the cheapest discriminating check for each, via debug_triage
user-invocable	true

/triage — Ranked Bug Triage

Collect the error/stack trace verbatim into error. Never trim the trace.
Gather cheap context: repro steps and recent changes (context), runtime/versions (runtime), and the implicated source (files with line ranges around the frames, e.g. 'src/app.ts:30-60').
Call debug_triage.
Relay the ranked hypotheses with their likelihoods, then run (or offer to run) the TOP hypothesis's discriminating check — logs, a breakpoint, a one-liner — before touching any fix.
If the check kills the top hypothesis, promote the named runner-up and check that one; only implement the minimal fix once a hypothesis is CONFIRMED. Then add the locking test the tool suggested.

Requires GROK_API_KEY (or XAI_API_KEY). If the tool returns its missing-key error, relay it and suggest /setup.