en un clic
devctl
devctl contient 13 skills collectées depuis godismyjudge95, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
How to write and run devctl integration tests — where tests live, how to write failing tests first (TDD), and how to run them safely inside an Incus container without touching live host data.
Full workflow for tagging and publishing a devctl release and/or a PHP binaries release — versioning, release note generation from TODO.md, clearing TODO.md completed items, and the exact git/GitHub CLI steps for each release type.
How to add a new CLI command to devctl — writing the Cmd struct, registering it with init(), adding Client methods, using output helpers, and documenting it in README.md
How to add a new dashboard screenshot for a new or existing feature — wiring up scripts/screenshots.js, seeding data into the demo container via scripts/demo.sh, and adding the image reference to the README.
How to create, update, or maintain agent skills for this project — file structure, frontmatter rules, naming constraints, and where OpenCode discovers them
Full workflow for picking up and completing a TODO item from TODO.md — read the backlog, clarify, implement, install, browser-test, update docs, and move the item to Completed.
How to keep README.md accurate and well-structured when devctl features change — canonical section order, per-section rules, source-of-truth files, style rules, and a pre-save checklist.
How to add a new managed dev service to devctl — writing the ServiceDefinition, registering it in config/defaults.go, and wiring up the optional installer
How to add or modify the devctl SQLite schema using goose SQL migrations and regenerate type-safe queries with sqlc
Patterns and conventions for working on the devctl Go backend — adding API endpoints, handlers, SSE/WebSocket, service management, and error handling
How to implement an idempotent APT-based service installer in devctl — the Installer interface, shared helpers, and registration in install.NewRegistry
How to test devctl features via the browser dashboard — always use the Playwright snapshot tool, never the screenshot tool, and always verify changes in the UI at http://127.0.0.1:4000 after deploying.
Patterns and conventions for working on the devctl Vue 3 SPA — Pinia stores, API wrappers, shadcn-vue components, Tailwind v4, and the Vite/go:embed pipeline