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

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

constraint-enforce

Étoiles6

Forks0

Mis à jour16 avril 2026 à 16:05

Use when the user asks to "/constraint-enforce", "enforce constraints", "run constraint tests", "跑 constraint 驗證", or "run constraint enforcement". Runs the 4-layer deterministic enforcement pipeline on generated constraint artifacts.

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

caasi

caasi/dong3

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

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	constraint-enforce
description	Use when the user asks to "/constraint-enforce", "enforce constraints", "run constraint tests", "跑 constraint 驗證", or "run constraint enforcement". Runs the 4-layer deterministic enforcement pipeline on generated constraint artifacts.

Constraint Enforce

You run the deterministic enforcement pipeline on generated constraint artifacts and report results.

Workflow

Detect language — check the repo's build files (package.json, dune-project, Cargo.toml, pyproject.toml, etc.) to determine the language. Use the toolchain matrix in constraint-generate/references/toolchain-matrix.md for the correct commands per layer per language.
Read references/enforcement-layers.md for the layer execution order and semantics
Run layers in order: Lint → Validation → PBT → Mutation Testing, using the detected language's tools
Fail fast: fix issues at each layer before proceeding to the next
For Layer 3+4 feedback loop: read references/mutation-feedback-guide.md
Default mutation score target: 80%
Max 3 feedback rounds
Escalation: after 3 rounds or on unresolvable mutants, report to user with mutant summary table

Final Report

For each layer:

Status: pass / fail
Mutation score (Layer 4)
Surviving mutants (if any)
Recommendations for next steps

Plus depuis ce dépôt

même dépôt

review-loop

caasi/dong3

General assisted review loop for changes — code or design artifacts (specs, plans, docs). Local reviewers answer blind and in parallel on the same unfixed diff, before any fix; the verdict names which reviewers actually ran. Convergence is each reviewer's own explicit per-round verdict, not the facilitator's round-count — the loop runs until-dry (K consecutive rounds where every live reviewer reports converged), with the facilitator owning K and the escalation-to-direction-guard decision. The roster is enrolled per host by `/review-loop:init`, which is never a precondition. For PR/MR targets a forge reviewer follows the local gate; GitHub Copilot is the built-in adapter and needs no enrollment. Findings say what would disprove them, and are reproduced before they are acted on. Never merges autonomously.

2026-07-216

tsugu

caasi/dong3

Git-native preparation & convergence — carry work forward across the gap when no human is watching, the handoff to a human, and the resume by whoever comes next. Use to prepare work before review, then converge it with the human, or run the lifecycle via `/tsugu:init`, `/tsugu:prepare`, `/tsugu:converge`, `/tsugu:prune`. Triggers on "prepare work before review", "carry work forward", "git-native preparation", "init/prepare/converge/prune", or "/tsugu". Human-triggered and schedule-wireable (wire `prepare` to a driver on the provisioned machine — local cron / `/loop` / `/schedule`). Invokes no user-installed skill by default — native git + its own built-in subagents only. Never auto-merges and never performs public coordination without approval.

2026-07-136

old-react

caasi/dong3

Use when reviewing or refactoring React code in pre-RSC projects (classes, hooks, Redux/MobX/observable, Reselect, Immer). Applies FP-thinking rules grounded in render purity, immutable updates, and the Elm Architecture (Model, Msg, update, view, Cmd, Sub). Triggers on phrases like "review my React code", "refactor this class component", "audit hooks usage", "review this reducer", or the slash command `/old-react`. Out of scope: React Server Components, the `use(promise)` hook, `'use client'` and `'use server'` boundaries.

2026-05-016

constraint-generate

caasi/dong3

Use when the user asks to "/constraint-generate", "generate constraint tests", "generate constraint artifact", "產生 constraint 的 test", or "generate test from constraint". Reads constraints/*.md and produces deterministic test artifacts.

2026-04-166

kami

caasi/dong3

Use when the user asks to "review my agent", "check if this design is responsible", "who does this affect", "is this agent ethical", "think about the impact", "reflect on this skill", "examine this agent's boundaries", mentions "/kami", "kami", "civic AI", "humane intelligence", "仁工智慧", or wants a Socratic dialogue about human-AI collaboration and stewardship. Other skills may suggest reflection, but only invoke when the user explicitly agrees.

2026-04-166

constraint-write

caasi/dong3

Use when the user asks to "/constraint-write", "write constraint", "define constraint", "幫我寫 constraint", "定義 constraint", or when the agent detects prohibition ("不能", "禁止", "must not"), obligation ("必須", "一定要", "always"), or invariant ("roundtrip", "idempotent") language in conversation and wants to suggest writing a constraint.

2026-04-166

name	constraint-enforce
description	Use when the user asks to "/constraint-enforce", "enforce constraints", "run constraint tests", "跑 constraint 驗證", or "run constraint enforcement". Runs the 4-layer deterministic enforcement pipeline on generated constraint artifacts.

Constraint Enforce

You run the deterministic enforcement pipeline on generated constraint artifacts and report results.

Workflow

Detect language — check the repo's build files (package.json, dune-project, Cargo.toml, pyproject.toml, etc.) to determine the language. Use the toolchain matrix in constraint-generate/references/toolchain-matrix.md for the correct commands per layer per language.
Read references/enforcement-layers.md for the layer execution order and semantics
Run layers in order: Lint → Validation → PBT → Mutation Testing, using the detected language's tools
Fail fast: fix issues at each layer before proceeding to the next
For Layer 3+4 feedback loop: read references/mutation-feedback-guide.md
Default mutation score target: 80%
Max 3 feedback rounds
Escalation: after 3 rounds or on unresolvable mutants, report to user with mutant summary table

Final Report

For each layer:

Status: pass / fail
Mutation score (Layer 4)
Surviving mutants (if any)
Recommendations for next steps