ring-verifying-code

Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGE_READY or NEEDS_FIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single command, or when already inside ring:running-dev-cycle (use its gates).

Ir para a instalação

Repositório: LerianStudio/ring
Última atividade na origem: 6 de junho de 2026 às 22:57
Idioma detectado do SKILL.md: inglês
Estrelas: 206
Forks: 26

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

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ê.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/LerianStudio/ring --skill ring-verifying-code

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

ring-declaring-plugin-permissions

Interactively authoring an access-manager permission-declaration manifest (permissions.yaml) for the access-manager "inversão de responsabilidade": drives a plugin team through discovering its real Authorize() surface, normalizing every action to the SEMANTIC standard (never HTTP verbs), declaring roles/group grants and the M2M contract, then emits and validates a manifest that matches the lib-auth/v3 auth/declaration schema. Use when a plugin must publish its own permissions at boot (WireFromEnv) instead of the access-manager seed owning them, or when writing/fixing a permissions.yaml. It also bumps the repo's github-actions-shared-workflows CI pin to the release carrying the permission-manifest nudge. Skip when the plugin has no auth guards, or you only need the wiring (see WireFromEnv) and the manifest already exists.

2026-08-11

ring-writing-plans

Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.

2026-07-02

ring-applying-licenses

Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no LICENSE. Skip when license, headers, and SPDX already match, or for non-code repos.

2026-07-02

Ver todas deste repositório

name	ring:verifying-code
description	Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGE_READY or NEEDS_FIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single command, or when already inside ring:running-dev-cycle (use its gates).

Code Verification

When to use

Before creating a pull request
After completing implementation and wanting to confirm everything passes
When user wants a quick "is this ready?" check

Skip when

Project is not Go (no go.mod found)
User only wants to run a single specific command
Already inside a ring:running-dev-cycle execution (use the cycle gates instead)

Complementary: ring:running-dev-cycle, ring:reviewing-code

Run everything. Get a verdict. This skill only REPORTS — it does NOT fix anything.

Step 0: Discover Commands

Verify go.mod exists → if not, STOP: "Not a Go project."
Read Makefile to discover available targets
Check tool availability: goimports, gofmt

Command resolution:

Check	Default	Makefile Override
Lint	`golangci-lint run ./...`	`make lint` if target exists
Vet	`go vet ./...`	`make vet`

#	Check	Fail Condition
1	Lint	Non-zero exit
2	Vet	Non-zero exit
3	Imports	Any output (files listed need fixing)
4	Format	Any output (files listed need formatting)
5	Docs	Files modified (docs were stale)
6	Unit Tests	Non-zero exit

#	Check	Notes
7	Integration Tests	DB, external services, testcontainers
8	E2E Tests	Full user flows

Condition	Verdict
All commands PASS (or SKIP for unavailable)	MERGE_READY
Any command FAIL	NEEDS_FIX
Target unavailable	SKIP — does not count as failure

ring-verifying-code

Opções de instalação

Revise os arquivos de origem

Code Verification

When to use

Skip when

Related

Step 0: Discover Commands

Code Verification

When to use

Skip when

Related

Step 0: Discover Commands

Phase 1: Static Analysis + Unit Tests (parallel)

Phase 2: Integration + E2E Tests (sequential)

Phase 3: Executive Summary

Verdict Rules

Error Display

ring-verifying-code

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Code Verification

When to use

Skip when

Related

Step 0: Discover Commands

Code Verification

When to use

Skip when

Related

Step 0: Discover Commands

Phase 1: Static Analysis + Unit Tests (parallel)

Phase 2: Integration + E2E Tests (sequential)

Phase 3: Executive Summary

Verdict Rules

Error Display