Use the GitHub CLI (gh) to manage issues, pull requests, labels, and repo metadata; includes safe body formatting with temp files or HEREDOCs to avoid shell mangling.
Guide through tasks where project dependencies must be added.
Manage Vikunja tasks, projects, and labels through the Vikunja REST API. Load always whenever the user mentions Vikunja, tasks, todos, task management, project organization, or asks to create/list/update/delete tasks and projects in Vikunja.
Perform deep best-practices audits for any software project (frontend, backend, APIs, mobile, data/ML, infra). Use when users ask to audit architecture, code quality, scalability, maintainability, reliability, security posture, or "what should be improved" across a codebase.
Guide Opencode through coding tasks where git should be utilized. Use when the user asks to implement a specific change and commit it, or says "commit this," "make the change and commit," or similar. Also use for branch creation, listing, cleanup, and management tasks.
Guide through tasks where database migrations must be added. Use when users ask to add migrations, run migrations, rollback changes, or modify database schema.
Reviews GitHub pull requests with structured findings on code quality, security, performance, and test coverage. Use when user asks to "review PR", "review pull request", "review 123", "review owner/repo#123", "review https://github.com/owner/repo/pull/123", or similar PR review requests. Always attempts to clone the repo and create a worktree for full git analysis before resorting to API-only review. Never proceeds with degraded review without explicit user permission.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Opencode's capabilities with specialized knowledge, workflows, or tool integrations.