ring:verifying-code
/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).
- Author
- LerianStudio ↗
- Repository
- ring ↗
- Licence
- Apache-2.0
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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).
Original author 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).
How it works
- 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
SKILL.md preview
--- 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) ## Related **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 1. Verify `go.mod` exists → if not, STOP: "Not a Go project." 2. Read `Makefile` to discover available targets 3. 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` | | Imports | `goimports -l .` | `make imports` | | Format | `gofmt -l .` | `make fmt` or `make format` | | Docs | `make generate-docs` | `make docs` | | Unit Tests | `go test ./...` | `make test-unit` or `make test` | | Integration Tests | `make test-integration` | — | | E2E Tests | `make test-e2e` | — | If Makefile target doesn't exist: use default command. If neither exists: SKIP (not a failure). ## Phase 1: Static Analysis + Unit Tests (parallel) Run all 6 in **parallel**. Capture stdout, stderr, exit code, duration for each. | # | 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 | Phase 1 gate: ALL pass → proceed to Phase 2. ANY fails → still run Phase 2, but verdict will be NEEDS_FIX. ## Phase 2: Integration + E2E Tests (sequential) Run sequentially. Continue even if first fails. | # | Check | Notes | |---|-------|-------| | 7 | Integration Tests | DB, external services, testcontainers | | 8 | E2E Tests | Full user flows | If target doesn't exist → SKIP (not a failure). ## Phase 3: Executive Summary ``` ============================================ VERIFICATION SUMMARY ============================================ Phase 1 — Static Analysis + Unit Tests: PASS / FAIL Phase 2 — Integration + E2E Tests: PASS / FAIL / SKIP Total time: Xs ┌───┬──────────────────────┬────────┬──────────┐ │ # │ Check │ Status │ Duration │ ├───┼──────────────────────┼────────┼──────────┤ │ 1 │ lint │ PASS │ 3.2s │ │ 2 │ vet │ PASS │ 1.1s │ │ 3 │ imports │ FAIL │ 0.4s │ │ 4 │ format │ PASS │ 0.3s │ │ 5 │ docs │ PASS │ 2.1s │ │ 6 │ unit tests │ PASS │ 8.5s │ │ 7 │ integration tests │ PASS │ 22.3s │ │ 8 │ e2e tests │ SKIP │ - │ └───┴──────────────────────┴────────┴──────────┘ ERRORS (first 10 lines per failure): ───────────────────────────────────── #3 imports: internal/handler/user.go internal/service/auth.go VERDICT: NEEDS_FIX ``` ## Verdict Rules | Condition | Verdict | |-----------|---------| | All commands PASS (or SKIP for unavailable) | **MERGE_READY** | | Any command FAIL | **NEEDS_FIX** | | Target unavailable | **SKIP** — does not count as failure | ## Error Display For each failed command: show first 10 lines of stderr (or stdout if stderr empty). - `goimports -l` / `gofmt -l` output = list of files to fix - `make generate-docs` changed files = list modified files
Versions
The database has no other skills named ring:verifying-code.
Database snapshot: 13.11.2026 · package version 58d43b3dd11e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before… - 90ring:running-dev-cycle-frontend
Running the frontend (React/Next.js/TS) dev cycle from a plan.md (ring:writing-plans format; legacy tasks.md only for in-flight cycles) or backend handoff: drives frontend agents through Gate 0 TDD plus accessibility/visual/E2E/perf checks, Gate 7 parallel review, and Gate 8… - 95verify
Run the full fuku verification loop (format, lint, vet, test, race, e2e, docs) before committing. Use when asked to verify changes, run lint, run tests, check that changes pass CI, or before any commit/push. - 100verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no… - 100release-check
Check if project is ready for release with comprehensive pre-release validation. Use when verifying release readiness, running validation checks, or checking project quality before publishing. - 90woocommerce-dev-cycle
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.