OpenCode plugin packages for AppVerk. The root plugin loads the AppVerk plugin bundle from this repository, which currently provides:

• A controlled commit workflow (/commit) that enforces AppVerk git policies.
• A Python development workflow (/python) with TDD, coding standards, and stack-specific patterns (FastAPI, Django, Celery, SQLAlchemy, Pydantic).
• A TypeScript + React development workflow (/frontend) with TDD, coding standards, and stack-specific patterns (Tailwind, Zustand, TanStack Query, React Hook Form, TanStack Router).
• A code review workflow (/review) with parallel security and quality audits, verification agents, fix commands, feedback analysis, and skill-agent integration.
• A QA workflow (/create-qa-plan, /run-qa) for end-to-end testing — generates test plans from PR descriptions and executes them via Playwright (frontend) or HTTP + DB (backend).
• A Swift development workflow (/swift) with TDD, coding standards, and modern Apple stack patterns (SwiftUI, @Observable, SPM, SwiftData).
• A global skill registry that makes all AppVerk development skills available to every OpenCode agent via a single load_appverk_skill tool, with mandatory activation rules injected into every agent's system prompt.

Add the root plugin package to your OpenCode config:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["av-opencode-plugins@git+https://github.com/AppVerk/av-opencode-plugins.git#v0.2.16"]
}

Restart OpenCode after updating the config. The root plugin installs the AppVerk plugin bundle and registers /commit, /python, /frontend, /swift, /review, /fix, /fix-report, and /analyze-feedback automatically.

Create a commit for the current repository changes:

/commit

Create a commit and append a work item reference:

/commit AV-42

The command uses the packaged AppVerk workflow, generates a Conventional Commit style message, and routes the final commit through the controlled runtime instead of allowing raw git commit from the bash tool.

Run the Python development workflow with TDD and stack-specific patterns:

/python Add user authentication endpoint with JWT

The /python command:

1. Detects your project stack (FastAPI, Django, Celery, etc.)
2. Loads relevant Python development skills
3. Follows TDD: writes tests first, then implementation
4. Runs quality gates (typecheck, tests, lint)

You can also invoke the agent directly:

opencode agent python-developer "Refactor user service to use repository pattern"

Run the TypeScript + React development workflow with TDD and stack-specific patterns:

/frontend Add user profile form with validation

The /frontend command:

1. Detects your project stack (Tailwind, Zustand, TanStack Query, etc.)
2. Loads relevant TypeScript + React development skills
3. Follows TDD: writes tests first, then implementation
4. Runs quality gates (typecheck, tests, lint)

You can also invoke the agent directly:

opencode agent frontend-developer "Refactor auth store to use Zustand"

Run the Swift development workflow with TDD and modern Apple stack patterns:

/swift Add user profile screen with SwiftData persistence

The /swift command:

1. Detects your project stack (SwiftUI, SwiftData, URLSession, etc.)
2. Loads relevant Swift development skills
3. Follows TDD: writes tests first, then implementation
4. Runs quality gates (build, tests)

You can also invoke the agent directly:

opencode agent swift-developer "Refactor networking layer to use async/await"

All AppVerk development skills are automatically available to every OpenCode agent (built-in and custom) through the load_appverk_skill tool. When any agent starts a chat session, mandatory activation rules are injected into its system prompt.

Load a skill manually at any time:

Use the load_appverk_skill tool with name "python-coding-standards"

Available skills include:

• python-coding-standards, python-tdd-workflow, fastapi-patterns, sqlalchemy-patterns, pydantic-patterns, async-python-patterns, uv-package-manager, django-web-patterns, django-orm-patterns, celery-patterns
• frontend-coding-standards, frontend-tdd-workflow, tailwind-patterns, zustand-patterns, tanstack-query-patterns, form-patterns, tanstack-router-patterns, pnpm-package-manager
• standards-discovery (code review)

Run a comprehensive code review with parallel security and quality audits:

/review Review the authentication module for security issues and code quality

The /review command:

1. Detects your project stack and loads relevant skills (Python, Frontend, PHP)
2. Launches security-auditor, code-quality-auditor, and optionally documentation-auditor agents in parallel
3. Runs verification agents (cross-verifier, challenger) to validate findings
4. Aggregates findings with unique issue IDs (SEC-001, ARCH-001, etc.)
5. Generates a structured markdown report
6. Optionally saves to docs/reviews/YYYY-MM-DD-<branch>.md

Fix a single issue by ID from a saved report:

/fix SEC-001

Or paste the full issue block directly:

/fix [paste issue block from /review or /run-qa]

Batch-fix issues from a saved report:

/fix-report docs/reviews/2026-04-22-feature-auth.md

Analyze PR comments and generate response drafts:

/analyze-feedback 123

Classifies each comment as "Address" or "Reject" and optionally publishes responses via GitHub CLI.

Generate a structured test plan from a PR description or ticket:

/create-qa-plan Add two-factor authentication to the login flow

The /create-qa-plan command:

1. Parses the feature description or ticket text
2. Generates test cases with preconditions, steps, and expected results
3. Writes the plan to docs/testing/plans/YYYY-MM-DD-<topic>-test-plan.md

Run a saved test plan or perform an ad-hoc QA check:

/run-qa docs/testing/plans/2026-04-29-feature-auth-test-plan.md

The /run-qa command:

1. Loads the test plan or creates a quick checklist for the given path
2. Detects whether the scope is frontend, backend, or both
3. Launches testing agents in parallel when both scopes exist (@qa-fe-tester and/or @qa-be-tester)
4. Executes tests using native Playwright tools (frontend) or native HTTP and DB CLI tools (backend)
5. Collects results into a markdown report with pass/fail status

You can also invoke testing agents directly:

opencode agent qa-fe-tester "Run accessibility checks on the checkout page"

opencode agent qa-be-tester "Test GET /api/v1/orders with pagination"

Note on Mode: Commands always appear in tab-completion. Agents marked primary also appear in tab-completion, while subagent agents are hidden and must be invoked explicitly (e.g., @fix-auto).

• packages/commit - plugin source, tests, command template, and build scripts for the commit workflow.
• docs/plugins/commit.md - package-level behavior and usage guide.
• packages/python-developer - plugin source, tests, skill files, and build scripts for the Python development workflow.
• docs/plugins/python-developer.md - package-level behavior and usage guide.
• packages/code-review - plugin source, tests, agent prompts, command template, and build scripts for the code review workflow.
• docs/plugins/code-review.md - package-level behavior and usage guide.
• packages/frontend-developer - plugin source, tests, skill files, and build scripts for the TypeScript + React development workflow.
• docs/plugins/frontend-developer.md - package-level behavior and usage guide.
• packages/skill-registry - global skill registry source, tests, and build scripts.
• docs/plugins/skill-registry.md - package-level behavior and usage guide.
• packages/qa - QA plugin source, tests, command templates, agent prompts, skills, and build scripts.
• docs/plugins/qa.md - package-level behavior and usage guide.
• packages/swift-developer - plugin source, tests, skill files, and build scripts for the Swift development workflow.
• docs/plugins/swift-developer.md - package-level behavior and usage guide.
• package.json - workspace definition and shared validation commands.

Install workspace dependencies:

npm install

Run the main validation commands:

npm run typecheck
npm run test
npm run build
npm run check

• Commit Plugin Guide
• Python Developer Plugin Guide
• Code Review Plugin Guide
• Frontend Developer Plugin Guide
• Skill Registry Plugin Guide
• QA Plugin Guide
• Swift Developer Plugin Guide

This repository currently does not include a top-level LICENSE file. Add one before publishing or distributing the packages beyond internal use.