backend-change-builder

Design backend changes with validation, authorization, transactions, and idempotency safeguards.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill backend-change-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-change-builder
Source: https://github.com/machenjie/rd-skills/tree/main/src/professional-skills/backend-change-builder
Command: npx skills add https://github.com/machenjie/rd-skills --skill backend-change-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents production incidents caused by incorrect backend behavior, including broken authorization, non-idempotent retries, partial writes, and opaque failures.

Core Features & Use Cases

It guides you to design and implement backend changes with explicit validation at trust boundaries, server-side authentication/authorization (including object-level IDOR prevention), clear transaction boundaries, robust idempotency for retriable mutations, and structured error/observability patterns. Use it when you are modifying endpoint handlers, service methods, authentication/authorization logic, permission checks, transactional data mutations, or background/async jobs that must remain correct under concurrency and retries. It is also suited for agent-assisted backend fixes where you need evidence, a same-pattern scan, and a reuse-and-placement rationale before accepting changes.

Quick Start

Use backend-change-builder to produce a backend implementation and review plan for updating an endpoint that mutates data with correct validation, authorization, transactions, idempotency, error handling, observability, and concurrency safeguards.

Frequently Asked Questions about backend-change-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design idempotent retries for backend API endpoints?

Designing idempotent retries for backend API endpoints requires explicit transaction boundaries and robust idempotency keys to ensure retriable mutations process safely without partial writes or duplicate side effects.

How do I prevent IDOR and broken authorization in domain services?

Preventing IDOR and broken authorization in domain services requires server-side authentication and object-level authorization checks to verify users cannot access or mutate resources outside their permitted trust boundaries.

What is the best way to handle partial failures in async background jobs?

The best way to handle partial failures in async background jobs is to apply structured error semantics and structured logging with correlation to track concurrency issues and safely retry failed operations without data corruption.

Does this approach work for agent-assisted backend fixes requiring evidence?

This approach works for agent-assisted backend fixes by generating an implementation and review plan that provides evidence, a same-pattern scan, and a reuse-and-placement rationale before accepting changes to mutating endpoints.

Why do I need explicit transaction boundaries for data mutations?

You need explicit transaction boundaries for data mutations to prevent production incidents caused by opaque failures and partial writes, ensuring that complex state changes across domain services either fully commit or safely roll back.