nexa-claude-go

Plugin nexa-claude-go from marketplace nexa-claude-marketplace in nexadevapp/nexa-claude-skills-marketplace. Commands read from the repo's manifest — 1 month ago.

Skills (19)

• audit

  Runs a comprehensive implementation audit for a delivered use case in a Go web application. Checks Definition of Done, i18n completeness and correctness, error message i18n, accessibility, visual fidelity against the design, htmx loading/error/empty states, and E2E traceability. Run after /deliver-u

• code-quality

  Runs golangci-lint v2 on Go files to fix lint errors, enforce a cyclomatic complexity limit with gocyclo, and apply consistent formatting with gofumpt and goimports; formats templ files with templ fmt. Use when the user asks to "lint", "format code", "run code quality checks", "run golangci-lint", o

• db-migration

  Creates goose SQL migrations and sqlc queries from the entity model, then regenerates the type-safe Go database code. Use when the user asks to "create a migration", "update the schema", "set up database tables", "write a goose migration", "add sqlc queries", or mentions schema migration, DB migrati

• deliver-cluster

  Delivers a cluster of use cases in parallel. Reads the dependency graph, works out which use cases can run at the same time, creates one git worktree per use case, runs /deliver-use-case in each, and feeds every finished branch to /merge-use-case one at a time. Repeats until the cluster is delivered

• deliver-use-case

  Orchestrates the full per-use-case delivery pipeline: writes the specification and the design if they are missing, implements the use case, writes E2E tests, and evaluates coverage against the spec. Iterates automatically until quality gates pass. The use case must be elaborated by /engineer-require

• implement

  Implements use cases and fixes bugs in a Go web application: sqlc queries, services, form validation, net/http handlers, templ views with htmx, and routes. Use when the user asks to "implement a use case", "fix a bug", "build the UI", "create an endpoint", "write a handler", "write a page", or menti

• integration-test

  Creates Go integration tests for net/http handlers, services, and sqlc queries against a real PostgreSQL database started with testcontainers-go. Use when the user asks to "write integration tests", "test with a real database", "create Go integration tests", or mentions Go integration testing, testc

• merge-queue

  Lands every branch that is ready, one at a time, when several agents have been working in parallel worktrees. Discovers the finished worktrees and the open pull requests, orders them so a dependency lands before what depends on it, and sends each through /merge-use-case under the merge lock. Use whe

• merge-use-case

  Merges a finished work item branch into main through a serial merge gate. Rebases the worktree branch onto main, resolves any conflict, runs the full unfiltered regression suite, fast-forwards main, closes the GitHub issue, and removes the worktree. Works for a use case, a technical task, a bug, or

• mutation-test

  Runs gremlins mutation testing on the Go business logic delivered for a use case to measure whether the unit tests actually detect broken behaviour, not just execute it. Reports the test efficacy and every surviving mutant with the assertion that would kill it. Runs automatically inside /deliver-use

• onboard-existing-app

  Retrofits an existing Go web application into the Nexa Agentic Engineering methodology by reverse-engineering a requirements catalog, entity model, use case diagram, and use case specs from the live code (routes, handlers, views, services, SQL migrations, and queries), and from BMAD-method artifacts

• playwright-test

  Creates browser-based end-to-end tests for a Go web application (templ + htmx) with Playwright for Go, covering complete user journeys from start to finish. The tests are Go tests behind the `e2e` build tag and run with `go test`. Use when the user asks to "write Playwright tests", "create e2e tests

• resolve-bug

  Orchestrates the full bugfix pipeline for a BUG-XXX or GitHub issue: an isolated tester reproduces the bug and updates the issue, a senior-dev agent writes a root-cause fix plan while a business-analyst agent links the affected requirement(s) in parallel, then the fix is implemented and gated on Def

• setup-arch-unit

  Sets up architecture rules for a Go project with the depguard and forbidigo linters of golangci-lint v2. Detects the package layout, proposes a default rule set derived from the Nexa Go conventions (no database access outside sqlc in feature code, no HTTP or templ in services, only internal/config r

• setup-env-profiles

  Sets up environment profiles (local, dev) for a Go project with database connection strings and environment-specific configuration, and scaffolds the config loader and the `cmd/dev` entry point. Local uses Testcontainers, dev uses Supabase. Only prompts the user for the Supabase connection strings.

• setup-i18n

  Sets up server-side internationalization for a Go web application with go-i18n: embedded TOML message catalogs, a locale detection middleware for net/http, context helpers that templ views call directly, and pluralization through CLDR rules. Run before implementing use cases so that every templ view

• setup-playwright-ci

  Generates a GitHub Actions workflow that runs the Playwright for Go end-to-end tests of a Go application on every pull request. The workflow sets up Go, installs Chromium through the pinned `go tool playwright`, runs `go test -tags=e2e` (which provisions PostgreSQL via Testcontainers), and uploads t

• setup-quality-ci

  Generates a GitHub Actions workflow that gates pull requests on Go code quality (golangci-lint, gofumpt/goimports and templ formatting, generated-code drift for sqlc and templ) and test coverage (go test with integration tests and an 80% threshold). Use when the user asks to "set up CI for code qual

• setup-web-middleware

  Builds the Go net/http middleware chain with authentication, authorization (RBAC), CSRF protection, security headers, structured slog logging, and panic recovery. Run before implementing use cases so that feature code can rely on cross-cutting infrastructure. Use when the user asks to "set up middle

Subagents (6)

• bug-analyst

  Independent senior-dev root-cause analyst. Reads a reproduced bug and the codebase, then posts a fix plan as a GitHub issue comment — never edits code. Follows bug-analyst's role in resolve-bug/SKILL.md as its binding operating manual.

• bug-tester

  Independent bug reproduction tester. Follows a bug report's reproduction steps against the running application — via browser for UI bugs, via HTTP for API-only bugs — and reports a Reproducible / Not Reproducible / Insufficient Information verdict with evidence. For docs auto-created from a raw GitH

• mutation-tester

  Independent mutation testing analyst for a delivered use case. Runs gremlins over the Go business logic delivered for the use case and reports the test efficacy plus every surviving mutant with the assertion that would kill it. Never writes tests and never edits production code. Follows mutation-tes

• playwright-test

  Independent Playwright E2E test author for a single use case of a Go (templ + htmx) application. Reads only the use case specification and frontend design — never implementation reasoning — so tests validate what was designed, not what was built. Follows playwright-test/SKILL.md as its binding opera

• requirement-linker

  Independent business-analyst agent. Cross-references a reproduced bug against docs/requirements.md and docs/use_cases/ to identify the affected requirement(s), links them into the bug report and the GitHub issue. Follows requirement-linker's role in resolve-bug/SKILL.md as its binding operating manu

• use-case-archaeologist

  Independent reverse-engineering agent for Go web applications. Given one feature cluster (a set of routes with their handlers, views, services, and queries, optionally seeded by a matching BMAD story), writes a single grounded UC-XXX spec cited to file:line, never invented. Writes only its own UC fi

MCP servers (1)

• playwright

  runs: npx @playwright/mcp@latest