How to read this page
Each module has a panel screen (when clicking makes sense) and the equivalent CLI commands. The panel never does
anything the CLI does not: every button triggers a deck command. All commands accept --help.
Servers and local environment
Dev Launcher (/launcher)
Shows the configured services and whether each port is responding: repositories with launch.port, the mocks and the
panel itself. Lets you start one or more repositories (each in a new terminal tab) and bring Docker Compose stacks up
or down.
| Command | What it does |
|---|---|
deck launch --repo web,api / deck launch-all | Starts the local servers of the chosen repositories |
deck compose up infra / deck compose down all | Docker Compose per stack (up, down, stop, restart, build, pull, ps, logs) |
deck open-emulator | Opens the configured Android emulator |
Mocks (/mocks)
Local HTTP servers with fixed responses per route, to simulate external integrations (payments, SAP, an identity provider…). The screen shows whether each mock is up, the declared routes, the requests received, and lets you clear that log.
| Command | What it does |
|---|---|
deck mocks | Starts every mock in deck.yaml (each with /__mock/requests and /__mock/reset) |
Multi-repository git
Git dashboard (/git-dashboard)
One row per repository: current branch, commits ahead and behind, local changes, upstream and stuck locks. Batch
actions: update all (stash, pull, reapply the stash), joint checkout of a branch, move everything back to the default
branch, normalize line endings, clean up merged branches and remove stuck index.lock files.
| Command | What it does |
|---|---|
deck git-dashboard --json | Status of every repository |
deck git-update-projects | Stash, pull and reapply the stash in all of them |
deck git-checkout-branch --branch <name> [--repo web,api] | Joint checkout |
deck git-checkout-dev / deck git-prune-branches / deck git-fix-lines / deck git-clean-locks | Batch maintenance |
Coverage (/cobertura)
Reads the JaCoCo, LCOV and Clover reports of each repository with coverage and shows lines, branches and methods,
with the report date. It can run the tests with coverage and open the HTML report inside the panel.
| Command | What it does |
|---|---|
deck coverage-status --json | Consolidates existing reports, without running tests |
deck git-test-coverage [--repo api] | Runs the tests with coverage |
Workflow and Azure Boards
Azure Boards (/boards)
The day-to-day flow of a task, with the board phases defined in deck.yaml:
The screen shows the card details (type, title, status, assignee, description) and lets you move it to any phase,
comment, assign it to yourself and start the flow. The branch name follows azureBoards.branchPattern (for example
{type}/AB#{id}-{slug}). With no associated card, the id 00000 turns off the board integration.
| Command | What it does |
|---|---|
deck git-workflow-start-dev --card <id> --repo <repo> | Creates the branch and moves the card to the phase with role: start |
deck git-smart-commit [--push] | Commit with the branch’s AB#id |
deck git-workflow-code-review --repo <repo> --title "..." | Opens the PR (GitHub or Azure Repos) and moves to review |
deck git-workflow-rework --repo <repo> --desc "..." | Records rework |
deck boards-move-card --id <id> --state "<phase>" | Moves the card (resolves column → System.State through the board mapping) |
deck boards-view-card, deck boards-my-cards, deck boards-card-status, deck features | Queries |
deck boards-cr create --id <card> --reviewer "<name>" | Code review subtasks per reviewer |
deck wiki task <id> / deck notify-prs <id> --send | Task file in the wiki and PR notice on Teams |
Cloud, CI/CD and logs
GitHub and PRs (/github-prs)
The team’s open PRs across all repositories (with review status, checks and conflicts), your PRs and the latest
GitHub Actions runs. Lets you dispatch a workflow on a branch. Queries use the gh already authenticated on the
machine.
Cloud logs (/cloud-logs)
Searches Azure Container Apps logs by environment and app (both from deck.yaml), filtering by text, level,
session id and user id. When the Azure CLI session expires, the screen offers device-code login without leaving the
panel.
| Command | What it does |
|---|---|
deck logs-search --env dev --app api --query-text "timeout" | Search |
deck logs-follow --env dev --app api | Follows live in the terminal |
deck azure-prs list / merge --repo api --id 12 --yes | Azure Repos PRs, with a minimum-approvals rule |
deck azure-pipelines run api --branch dev / logs api | Pipelines and logs of the failed step |
deck sonar check api | Quality Gate and key metrics |
deck prs-manage --json / deck monitor-pipelines | GitHub PRs and pipelines |
E2E tests
Runs (/testes) and history (/historico)
Deck has no scenario table: it discovers tests by running playwright test --list inside the repository set in
e2e.repo. You pick one or more tests, the environment and, optionally, debug mode (visible browser, one worker).
BASE_URL is resolved on the server from the chosen environment.
Only one run happens at a time; the “Abort” button stops Playwright and its browser. Each run goes into the history
with its duration, output and, when it fails, Playwright’s error-context.md files, which remain available even after
Playwright cleans up its results folder.
| Command | What it does |
|---|---|
deck tests list | Lists the test files; the ID is the file name (login.spec.ts → LOGIN) |
deck tests run <ID...> --env <environment> / run --all | Runs one or more files (the panel lets you pick individual tests) |
deck tests history | The same history as the panel |
Data and database
Database and diagnostics (/database)
PostgreSQL connection profiles (database.profiles), a catalog of parameterized diagnostic queries and a SQL editor.
Queries run in a read-only transaction; writes require confirmation on screen and never apply to production profiles.
The project catalog comes from a versioned JSON file; queries created or edited in the panel go to a local file and do
not change the catalog.
The “Connect” screen generates configuration for DBeaver, VS Code, DataGrip, pgAdmin, TablePlus, psql, .env and
Spring Boot, always with the <senha> placeholder instead of the password, which never leaves the server.
| Command | What it does |
|---|---|
deck db query -p hml --sql "select ..." | Free query (read-only) |
deck db run <id> -p hml --param status=A | Catalog query |
deck db tables / describe <table> / test <profile> | Exploration |
deck db script seed -p local --write | SQL scripts (seed, load), in a transaction, never in production |
deck db shell -p local | Interactive shell |
Setup and diagnostics
Environment setup (/setup-env)
Machine diagnostics in three groups: secrets, tools (with minimum versions, from tools in deck.yaml) and
cloned repositories. The screen installs what can be installed without interaction (JDK 17/25, Node 22 and Go
toolchains, Terraform, Git), reinstalls a broken tool, migrates a manual setup to the standardized toolchains and
configures the projects folder. Logins (gh, az), PAT and windowed installers remain in the terminal.
| Command | What it does |
|---|---|
deck diag --json | Full diagnostics |
deck setup all --yes | Wizard: runs only the pending steps |
deck setup toolchains / reinstalar <tool> / migrar | Standardized toolchains in ~/.deck/toolchains |
deck setup clone | Clones the repositories in deck.yaml |
deck secrets set <NAME> / materialize / capture | Secrets outside the repository and the repos’ sensitive files |
deck CLI (/cli)
Shows the installed version, the update channel (stable or dev) and the version’s changes, and lets you update, roll back to the previous version and download the binaries of the latest release.
Standards
Skills and standards (/skills)
Edits the team’s AI agent skills (SKILL.md and supporting files in .claude/skills/), so everyone uses the same
instructions with Claude Code and other agents.