backend-change

Implements Multica backend changes across Go handlers, services, migrations, CLI, and daemon workflows.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill backend-change-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-change
Source: https://github.com/vovanostm-public/multica/tree/main/.agents/skills/backend-change
Command: npx skills add https://github.com/vovanostm-public/multica --skill backend-change-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend changes in the Multica platform span many layers—HTTP handlers, use-case services, SQL migrations, CLI, daemon, and MCP integrations—and making changes without a consistent workflow leads to fat handlers, broken transactions, and missed migration steps. This Skill enforces the existing server architecture so changes land in the right layer with proper tests. ## Core Features & Use Cases - Layered backend workflow: Routes changes to the correct role (handler, use case, policy, persistence, adapter, CLI, daemon, MCP) while keeping HTTP handlers thin and transactions scoped to one business operation. - Schema and query changes: Guides adding up/down migrations, updating sqlc queries, running make sqlc, and updating handlers, converters, and tests in the same slice. - Integration automation scripts: Provides TypeScript agent scripts for task bootstrap, direct_merge smoke testing, and blocked-issue reruns instead of manual psql or gh commands. - Use Case: When adding a new API endpoint that requires a database column, follow the workflow to write the migration, regenerate sqlc code, implement the use case, and run focused Go tests before handing off to QA. ## Quick Start Ask the agent to implement a backend change such as adding a new field to an issue endpoint, and it will follow the migration, sqlc, handler, and testing workflow automatically.

Frequently Asked Questions about backend-change

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

FAQPage Schema
How do I make a backend change in the Multica Go server?▼

Identify the backend role being changed (handler, use case, policy, persistence, adapter, CLI, daemon, or MCP), keep HTTP handlers thin, and move multi-step policy into use-case code. Run focused Go tests first, then broader tests when risk justifies it.

How do I add a database migration with sqlc in a Go project?▼

Add both up and down migrations, update the sqlc queries, run `make sqlc` to regenerate code, and update handlers, converters, and tests in the same change slice. This keeps schema and query changes consistent.

What scripts validate the direct_merge integration flow?▼

Use `pnpm codex:integration-smoke -- --dry-run` followed by a full run to validate the done-to-daemon-push-to-merged flow without a PR. For stuck integrations, run `pnpm codex:integration-inspect -- --issue-number N`.

What prerequisites do the Multica agent scripts require?▼

The scripts require a running API server, a token in `~/.multica/profiles/local/config.json`, git SSH access to the project repo, and a bare cache under `~/multica_workspaces_local/.repos/`. Stop the daemon during worktree prep; the script starts it for the integration push.

When should I not modify auth and profile resolution in CLI changes?▼

Preserve existing auth and profile resolution for CLI and daemon changes unless the task explicitly changes it. Altering this behavior unintentionally can break authentication across daemon and integration flows.