CtrlK
BlogDocsLog inGet started
Tessl Logo

sporkwace/guv

enforces engineering-governance checks before code changes that may be unnecessary, risky, architectural, or scope-widening. use when the user asks whether to refactor, clean up, redesign, choose a next development step, review a proposed implementation, evaluate architectural consistency, review a pull request, or prevent development drift. do not use as the primary implementation skill for routine debugging, bug fixes, feature coding, or language-specific coding unless a no-op, minimal-diff, or architecture-conflict judgment is needed.

98

1.33x
Quality

100%

Does it follow best practices?

Impact

96%

1.33x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-1/

{
  "context": "Checks whether the agent recognizes when a cleanup request does not justify code changes and produces a concise governance review instead of editing for style.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Purpose",
      "description": "Identifies that the request is about cleanup rather than a concrete defect",
      "max_score": 10
    },
    {
      "name": "No benefit",
      "description": "States that there is no material defect, risk, or benefit",
      "max_score": 10
    },
    {
      "name": "No-op check",
      "description": "Includes an explicit no-op assessment",
      "max_score": 10
    },
    {
      "name": "Architecture impact",
      "description": "Mentions architecture constraints affected, even if none are changed",
      "max_score": 10
    },
    {
      "name": "Risks",
      "description": "Mentions risks or conflicts in the review",
      "max_score": 10
    },
    {
      "name": "Smallest change",
      "description": "States the smallest safe change as no change",
      "max_score": 10
    },
    {
      "name": "Acceptance test",
      "description": "Includes an acceptance test or indicates that existing tests are sufficient",
      "max_score": 10
    },
    {
      "name": "Recommendation",
      "description": "Recommends no change",
      "max_score": 10
    },
    {
      "name": "No-op value",
      "description": "Treats no-op as a valid successful outcome or better than an unnecessary diff",
      "max_score": 10
    },
    {
      "name": "Style pushback",
      "description": "Rejects cleanup justified only by style, polish, or modernization and notes the code is already in good shape",
      "max_score": 10
    }
  ]
}

evals

scenario-1

criteria.json

task.md

README.md

SKILL.md

tile.json