devrites-doubt

Name: devrites-doubt
Rating: 5 (1 reviews)
Author: ViktorsBaikers

Stress-test a single non-trivial decision via CLAIM → EXTRACT → DOUBT → RECONCILE → STOP with `devrites-doubt-reviewer` for an independent take. Use when the user says "are we sure", "double-check this", "what could go wrong", or a boundary / data-model / auth / public-API / migration change is about to commit. Not for post-merge review or trivial choices.

1stars

Updated 14 days ago

View on GitHub ↗License: NOASSERTION

How to add

/plugin marketplace add ViktorsBaikers/DevRites

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/devrites-doubt/svg)](https://www.skillteca.com.br/skills/devrites-doubt?utm_source=badge&utm_medium=readme&utm_campaign=badge)

#ai #test #api

Related skills

See all in Automação →

MoneyPrinterTurbo

84.1k

利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.

Automaçãoby harry0703

weather-svg-creator

55.6k

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

Automação#aiby shanraisshan

telegram-bot-builder

39.2k

Expert in building Telegram bots that solve real problems - from

Automação#github#gitby sickn33

segment-automation

39.2k

Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.

Automação#github#gitby sickn33

Category alert

Get new Automação skills every Monday

One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

devrites-doubt — CLAIM → EXTRACT → DOUBT → RECONCILE → STOP

A pre-mortem on a single decision, not a final review. Find what's wrong before it's load-bearing.

When to use

Introducing branching logic · crossing a module/service boundary · changing the data model · modifying auth/authz · changing a public API · touching migrations · changing a browser/user flow · relying on an assumption tests can't prove · working in unfamiliar code · claiming "this is safe", "this scales", or "this matche

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.