AI Agent Workflow Collection

Add GitHub-linked AI co-authors to Git commit trailers without inventing provider identities. Use whenever an AI agent that created or materially changed committed content writes, amends, or reviews a commit message. Trust the repository registry for known agents and defer missing-agent discovery to the register-ai-agent skill.

Decide whether a need is met by the standard library, an existing dependency, a new third-party library, or an internal implementation — and which package to pick when importing. Use it whenever a change adds a library, weighs build-vs-buy, swaps an internal helper for a dependency (or back), or picks between competing packages. Feeds plan-feature's build-vs-buy section.

Vocabulary, invariants, and operator runbook for the cross-repo landing saga: how a multi-repo Epic lands atomically, recovers from a partial landing, rolls back, and releases through the a-novel-kit/workflows actions (merge-gate, epic-freeze, epic-rollback, release-train, the AGENTKILLSWITCH halt). Load it when a change spans several repos under one Epic. It owns the saga vocabulary and the Epic Atomicity Rule, and defers version mechanics to manage-versions, per-repo release mechanics to prepare-release.

Cross-repo version management for a-novel / a-novel-kit. Load it whenever a change spans repos that must stay version-compatible to merge — an unreleased golib or pkg/go dependency, a proto or REST contract change, a breaking change to a published symbol. Covers git-tag semver, exact go.mod pins, commit-SHA pseudo-versions, the dependency-releases-FIRST merge order (the consumer re-pins to the released tag), and staged rollouts. Pairs with git-conventions, implement-feature, open-pull-request, write-.

REQUIRED for all pull requests. Always use when opening PRs, creating merge requests, or executing gh pr create / glab mr create commands. Enforces conventional branch names and conventional-commit PR titles.

Discover, programmatically verify, and register a GitHub-linked AI co-author identity. Use only when attribute-ai-commits reports status missing for the current agent, or when explicitly asked to add a new agent to the repository co-author registry. Publish the registry change through a pull request.

Canonical reference for the a-novel CLI. ALWAYS load alongside any skill that runs tests, builds artifacts, releases, or starts/stops local services. Covers the groups test, build, publish, repo (repository config, rulesets, required checks), run (daemon-backed start/kill/logs/env/volume/ui) and core (daemon lifecycle). Prefer a-novel over raw commands; lint/format/generate live in pnpm scripts (pnpm lint:go, pnpm format:go), never in Makefiles — deleted from every repo.

Write, review, and maintain Bash shell scripts for Agora backend services. Use whenever creating or editing any .sh file — test runners, build or publish scripts, entrypoints, env setup. Covers error handling, cleanup traps, argument validation, service readiness waits, and portability.

Write, review, and maintain Dockerfiles and compose files for Agora backend services. Use whenever creating or editing anything in builds/ — Dockerfiles, podman-compose files, database init scripts, entrypoint scripts. Covers Go service, job, database, and standalone dev images, and the compose files wiring them together.

Write and maintain GitHub Actions workflows, composite actions (action.yaml), and repo CI config across the a-novel / a-novel-kit orgs. Use whenever adding or editing a workflow, a shared action in a-novel-kit/workflows, a CI job, a required check, or a ruleset.

Base Go conventions for EVERY Go repo in the a-novel and a-novel-kit orgs — naming, error handling, dependency policy, context, the format/lint discipline, time, and secrets. Load it for ANY Go work in either org, alongside the matching repo-kind skill: write-go-service (a-novel services) or write-go-kit (a-novel-kit libraries — golib, jwt). Pairs with write-go-tests and document-code. Not JS/TS, SQL (write-sql), Protobuf (write-proto), Dockerfiles (write-dockerfiles), or shell scripts (write-bash-scripts).

Go conventions for the a-novel-kit shared-library repos under kit/ (golib, jwt, ...) — the golib-stays-minimal bar, the stricter kit dependency policy, graduating a sub-package into its own community package, and kit test conventions. Load it to write or review Go there, or to decide whether something belongs in golib at all. ALWAYS load write-go alongside it; a-novel services use write-go-service. Pairs with write-go-tests, document-code, manage-versions. Not JS/TS, kit/nodelib, or kit/workflows.

Clean-architecture conventions for the a-novel backend SERVICES — app/service-, app/platform-, and any repo with the cmd/internal/{config,lib,dao,core,handlers,models}/pkg layout. Load it for Go work there: endpoints, schema changes, business logic, new layers, REST/gRPC handlers, DAO tests. Covers the layer split and import direction, the interface+implementation pattern, transaction scoping, OpenTelemetry, and the service security model. Load write-go alongside; write-go-kit is the a-novel-kit library counterpart.

Test conventions for ALL Go code in the a-novel and a-novel-kit organizations — file/function naming, table-driven structure, mockery, assertions, parallelism, cross-package fixtures, helpers, coverage. Load it whenever writing or modifying a Go test file in a backend service OR a shared library. Pairs with write-go; layer-specific patterns live in write-go-service. Does NOT apply to JS/TS tests.

Write, review, and maintain any Agora service's JavaScript/TypeScript REST client package. Use whenever creating or editing files under pkg/js/ — the published client library (pkg/js/rest/), its integration tests (pkg/js/test/rest/), or the package and build config. Covers API methods, type definitions, exports, and test cases.

Write, review, and maintain the OpenAPI 3.1 specification for Agora backend services. Use whenever editing openapi.yaml — adding endpoints, parameters, schemas, responses, or updating descriptions and examples. Covers the REST public API only; gRPC contracts belong to the write-proto skill.

Write, review, and modify Protobuf definitions for Agora backend services. Use whenever creating or editing .proto files — new RPCs, messages, shared types, enums, or breaking-change assessment. Covers internal/models/proto/ and the buf toolchain.

Write, review, and maintain PostgreSQL SQL for Agora backend services. Use whenever creating or editing SQL — DAO query files (internal/dao/.sql), schema migrations (internal/models/migrations/.sql), or raw SQL embedded in Go: SELECT/INSERT/UPDATE/DELETE queries, DDL (tables, views, indexes, constraints), materialized views, pgcron jobs.