convez.ai
SkillAutomaçãoAvançado
cskwork

Superloop Skill

cskwork/superloop-skill

Uma unidade verificável de trabalho por tick, com ledger durável e gates de aprovação

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill para Claude Code que impõe um contrato verificável em cada tick de `/loop`, garantindo uma unidade de trabalho por ciclo registrada em ledger durável. Previne reprocessamento, trabalho não verificado e execução de tarefas fictícias através de regras claras de orientação, execução, verificação e gravação.

Instalação

$npx convez-ai cskwork/superloop-skill

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
1
Acompanhando
0
Saúde
28%
Último commit
há 4 semanas
Versão
v0.1.0
Issues abertas
0
Contribuidores
1

Casos de uso

  • Automação de ciclos de desenvolvimento com verificação de qualidade em cada iteração
  • Manutenção de documentação sincronizada com commits recentes
  • Detecção e correção automática de code smells em código tocado
  • Pipeline de tickets Jira com gates de consentimento de deploy
  • QA contínua de commits com rastreamento de blast radius e efeitos colaterais

Veredito

Superloop é uma ferramenta sofisticada para disciplinar loops autônomos, prevenindo falhas previsíveis com abstrações sólidas de ledger e verificação real. Ideal para equipes que precisam de automação confiável com rastreabilidade completa, mas exige familiaridade com shell scripting e conceitos avançados de runtime.

README

A tradução para o português deste README ainda está na fila.

superloop-skill

A Claude Code skill that puts a contract on every /loop tick.

/loop is the heartbeat (when to wake up); superloop is the discipline behind each beat (what to do, how much, how to verify and record). Built as a loop-native extension of supergoal-skill's baseline-first principles.

Landing page: https://cskwork.github.io/superloop-skill/ (KO default, EN toggle) · 한국어 문서: README.ko.md

Why

Unattended loops fail in predictable ways: they redo finished work after compaction, mark unverified work done, batch half-finished changes, or invent work to look busy. superloop prevents all four with one rule set:

  • One unit of work per tick - the smallest independently verifiable unit; never batch.
  • Ledger before memory - durable state in .superloop/<mission>/ledger.md survives context compaction; an idempotent queue means a re-fired tick never redoes finished work.
  • Ground truth per tick - no done without test/build/HTTP/DB evidence.
  • Gates outrank autonomy - pushes, merges, deploys, and issue transitions pause as awaiting-approval; the ticket pauses, the loop keeps working.

Tick anatomy

Every tick, every mission:

ORIENT -> PICK -> EXECUTE -> VERIFY -> RECORD -> PACE
StepDoes
ORIENTRead the ledger; reconcile against reality (git wins)
PICKOne open unit; empty queue backs off, never invents work
EXECUTEsupergoal discipline: smallest correct change, failing test first
VERIFYReal tests / builds / HTTP bodies / read-only DB evidence
RECORDAppend-only tick log, advance the cursor, point to evidence
PACECache-aware delays; Monitor instead of polling for events

Missions

LaunchMission
/loop 1d /superloop docsKeep changelog / wiki / READMEs in step with recent commits
/loop 1h /superloop smellsFind one bug or code smell in recently-touched code, fix it red-green
/loop 30m /superloop qaQA commits since the last verified SHA: intent, blast radius, side effects
/loop /superloop jiraOne ticket per tick through a 12-stage pipeline with a non-skippable deploy consent gate
/superloop <mission>Single tick, right now

Structure

SKILL.md                      # mission table + tick anatomy + safety rails
reference/loop-runtime.md     # distilled built-in /loop mechanics + cache-aware pacing + Monitor rules
reference/state-ledger.md     # ledger schema, idempotency, reconciliation
reference/mission-{docs,smells,qa,jira}.md
templates/{ledger,tick-report}.md
tests/*.test.sh               # contract tests (69 assertions) pinning the core rules

Install

git clone https://github.com/cskwork/superloop-skill
ln -sfn "$(pwd)/superloop-skill" ~/.agents/skills/superloop
ln -sfn ~/.agents/skills/superloop ~/.claude/skills/superloop

Pairs best with supergoal-skill (execution discipline is delegated to it).

Tests

for t in tests/*.test.sh; do bash "$t"; done

Contract tests fail if the skill ever loses its mission table, tick anatomy, one-unit rule, ledger, consent gates, or the jira pipeline stages.

Ver o original no GitHub

Bom para

Relacionados