Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

hima-triage

Estrelas1

Forks0

Atualizado2 de julho de 2026 às 18:59

For bug reports and runtime failures, enforce root-cause-before-fix — reproduce, isolate cause, fix minimally, add a regression test.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

momomuchu

momomuchu/hima

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	hima-triage
description	For bug reports and runtime failures, enforce root-cause-before-fix — reproduce, isolate cause, fix minimally, add a regression test.
stage	meta
source	base
mode	force

Purpose

Stop the jump-straight-to-patch reflex on bug reports. Forces reproduction and root-cause isolation before any fix is written, so the fix addresses the actual defect, not its symptom.

When to use

Any triggering input that is a bug report, crash, or regression — forced regardless of criticality (T through C).
Runtime failures surfaced by tests, logs, or user report.
Not for net-new feature work — that routes through hima-charter/hima-forge instead.

Steps

Reproduce the failure first — a fix without a reproduction is a guess.
Isolate the root cause: trace back from the failure to the actual defect, not the nearest plausible symptom.
Write the minimal fix that addresses the isolated cause — resist scope creep into unrelated cleanup (that's hima-purge's job, in its own commit).
Add a regression test that fails before the fix and passes after — this is the proof, not an assertion.
Re-run the full relevant test suite to confirm no new breakage.

Done when

The failure is reproduced, root cause is named (not assumed), and a regression test exists that would have caught it.
The fix is committed as B (behavioral), separate from any structural cleanup.

Mais deste repositório

mesmo repositório

hima-admit

momomuchu/hima

Bootstrap a new project or catch up an agent on an existing one in minutes by reading vision/goals/state and scaffolding the minimum brain files.

2026-07-021

hima-blueprint

momomuchu/hima

Produce the structural plan — component boundaries, contracts, data flow — plus a lightweight decision record, from a sealed charter.

2026-07-021

hima-charter

momomuchu/hima

Formalize intent into a spec artifact (Gherkin scenarios, acceptance criteria, criticality tags) before any non-md file may change.

2026-07-021

hima-covenant

momomuchu/hima

Declare and audit the per-project disciplines (cadence, branching, testing, architecture, methodology) that the pluggable StageSkillMap resolves against.

2026-07-021

hima-forge

momomuchu/hima

Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.

2026-07-021

hima-lookout

momomuchu/hima

Cited, multi-source research pass for H/C decisions or true blockers — converts findings into requirements, risks, and rejected alternatives.

2026-07-021

name	hima-triage
description	For bug reports and runtime failures, enforce root-cause-before-fix — reproduce, isolate cause, fix minimally, add a regression test.
stage	meta
source	base
mode	force

Purpose

Stop the jump-straight-to-patch reflex on bug reports. Forces reproduction and root-cause isolation before any fix is written, so the fix addresses the actual defect, not its symptom.

When to use

Any triggering input that is a bug report, crash, or regression — forced regardless of criticality (T through C).
Runtime failures surfaced by tests, logs, or user report.
Not for net-new feature work — that routes through hima-charter/hima-forge instead.

Steps

Reproduce the failure first — a fix without a reproduction is a guess.
Isolate the root cause: trace back from the failure to the actual defect, not the nearest plausible symptom.
Write the minimal fix that addresses the isolated cause — resist scope creep into unrelated cleanup (that's hima-purge's job, in its own commit).
Add a regression test that fails before the fix and passes after — this is the proof, not an assertion.
Re-run the full relevant test suite to confirm no new breakage.

Done when

The failure is reproduced, root cause is named (not assumed), and a regression test exists that would have caught it.
The fix is committed as B (behavioral), separate from any structural cleanup.