Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

$pwd:

bug-classification

Name: Bug Classification
Author: specula-org

// Severity classification of bugs already confirmed by Phase 4a. Use when: (1) Phase 4a (bug-confirmation) has produced confirmed-bugs.md and each entry needs a Severity tier, (2) producing the input for downstream submission filtering, (3) re-classifying bugs after status changes (e.g., REPRODUCTION FAILED → REPRODUCED on retry).

In Manus ausführen

$ git log --oneline --stat

stars:170

forks:21

updated:18. Mai 2026 um 08:56

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	bug-classification
description	Severity classification of bugs already confirmed by Phase 4a. Use when: (1) Phase 4a (bug-confirmation) has produced confirmed-bugs.md and each entry needs a Severity tier, (2) producing the input for downstream submission filtering, (3) re-classifying bugs after status changes (e.g., REPRODUCTION FAILED → REPRODUCED on retry).

Read guide.md for the full classification methodology.

related-skills.json

gleiches Repository

bug-confirmation.md

from "specula-org/Specula"

Bug confirmation and reproduction. Use when: (1) a bug has been found by model checking and needs code-level validation, (2) reproducing a bug in the real system to confirm it is not a false positive, (3) assessing whether a TLA+ counterexample maps to a real triggerable scenario.

2026-05-20170

harness-generation.md

from "specula-org/Specula"

Trace harness generation (Phase 2.5). Use when: (1) instrumenting a system's source code to emit NDJSON traces for TLA+ trace validation, (2) writing test scenarios that exercise protocol code paths, (3) producing the first batch of traces from instrumented tests.

2026-05-20170

tla-checking-workflow.md

from "specula-org/Specula"

TLA+ Model Checking workflow. Use when: (1) running TLC model checking or simulation on a TLA+ spec, (2) analyzing counterexamples from invariant violations, (3) determining whether a violation is a spec issue, an overly-strong invariant, or a real bug in the system implementation.

2026-05-20170

tla-trace-workflow.md

from "specula-org/Specula"

TLA+ Trace Validation workflow. Use when: (1) validating if a trace matches a TLA+ spec, (2) debugging trace validation failures (TLC reports 'Temporal properties were violated' or validation stops unexpectedly), (3) fixing spec/trace inconsistencies after root cause is identified.

2026-05-20170

tla-verification-workflow.md

from "specula-org/Specula"

TLA+ Verification workflow (orchestration). Use when: running the full verification loop — iterating between trace validation and model checking until both pass, ensuring spec faithfully models the system.

2026-05-20170

code-analysis.md

from "specula-org/Specula"

Code analysis for formal verification. Use when: (1) investigating a system implementation to identify what to model in TLA+, (2) performing bug archaeology on a codebase, (3) producing a modeling brief that guides spec generation.

2026-05-18170

package.json

"author": "specula-org"

"repository": "specula-org/Specula"

GitHub-Repository öffnen Creator-Repositorys ansehen

$ install --global

$ download --local

In Manus ausführen

$ useful --forSOC

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe15-1253L4

Jeden Skill mit einem Klick ausführen

bug-classification

Mehr aus diesem Repository

Mehr aus diesem Repository