Backend change safety

Skill jukrap/ai-agent-playbook/skills/backend/backend-change-safety

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install

npx -y skills add jukrap/ai-agent-playbook --skill backend-change-safety

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when changing backend services, modules, workers, scheduled jobs, integrations, queues, configuration, or server-side business logic.

SKILL.md

2.0 KB, as published. Nobody here has run it

Backend Change Safety

Use this as the primary backend skill for non-trivial server-side changes that are not only API mapping or server-rendered flow work.

Workflow

Identify entrypoints, owners, runtime mode, data stores, side effects, and downstream consumers before editing.
Classify the change as additive, compatible, behavior-changing, destructive, operational, or integration-facing.
Keep controllers, services, repositories, workers, config, and module entrypoints in their existing responsibility boundaries.
Verify request paths, async paths, retries/idempotency, permissions, configuration, logs/metrics, and rollback shape.
Use request-validation-error-contract for request parsing, validation, and client-visible error changes.
Use job-worker-reliability for jobs, workers, queues, schedulers, retries, and dead-letter paths.
Load the relevant stack profile from references/stacks/ only after the repository stack is known.

Reference

Read references/backend-change-checklist.md before implementing or reviewing backend changes with shared runtime, persistence, or integration risk.

Read references/api-versioning-compatibility.md when a route, DTO, SDK, event, webhook, or client-visible payload may need compatibility handling.

Read references/transaction-side-effect-boundary.md when persistence, external side effects, events, jobs, or retries must stay consistent.

Read references/config-cache-runtime-contracts.md when changing configuration, feature flags, caches, process startup, or runtime defaults.

Read references/stack-profile-selection.md when the repository stack is known and you need to choose a Java, Kotlin, Node, Python, Go, .NET, or PHP profile.