ViktorsBaikers

DevRites — Testing skill for Claude Code

Testing community

Stop your AI from shipping half-baked code.

How to install DevRites

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ViktorsBaikers/DevRites and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What DevRites does

Stop your AI from shipping half-baked code. A disciplined senior-engineer workflow for Claude Code (spec, vet, build, prove, review, seal, ship) that keeps each feature's state on disk, catches spec drift mid-build, gates every phase on your project's principles, and refuses to claim "done" without proof.

Alternatives in Testing

Gstack — 15,000+ Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release Manag 33.9k ★
Debug — You are tasked with helping debug issues during manual testing or implementation 10k ★
Maestro Spec — Intent-driven spec precipitation — state a constraint in natural language (加一条规范：禁止用 any / 记录架构约束：服务间走 gRPC / 530 ★

README

DevRites

DevRites is a repository-local workflow for building software with Claude Code or Codex. It turns a feature request into a spec, a sliced plan, working code, recorded proof, a release decision, and an explicit ship step.

The work lives under `.devrites/`, not in chat history. A later session or a different agent can read the same plan, decisions, state, and evidence before it continues.

The core path is:

`SPEC -> CLARIFY -> [TEMPER] -> DEFINE -> VET -> BUILD -> PROVE -> POLISH -> REVIEW -> SEAL -> SHIP`

Clarify is mandatory but adaptive, so it asks no questions when the contract is complete. Temper adds an optional strategic review. Vet is the only final readiness phase before Build.

Seal decides whether the feature is ready without changing git. Ship first runs a read-only preflight and discloses the exact Git attempt. A fresh literal `GO` then authorizes one attempt to collapse eligible checkpoints, stage and validate the exact candidate, commit and reverify it, perform any approved project-conventional push, tag, or PR action, and archive the workspace. Unattended runs may create local WIP checkpoint commits along the way, but they remain local unless Ship's disclosed plan includes an approved remote action.

**Status:** [`v4.5.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.5.0): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.

This is the latest published release; `main` may contain unreleased work.