arka ci command mirrors the GitHub Actions gate more closely. Use arka review for local diff review, and arka route audit when you want to check fish/Python/test parity.
Natural language
CLI commands
Related Arka developer tools
Arka runs Ruff and Pytest through the active Python interpreter, so the local
gate uses the same virtual environment as the
arka installation. Use
--full before a release or merge to run the complete test suite.
External developer-tool catalog
Arka recognizes the common tools engineers already use around the terminal:
Use:
arka dev-doctor still focuses on the
repository gates that matter for the current project.
Detected tools
Arka looks for:- Python:
pytest,unittest,ruff,flake8 - Node:
npm test,npm run lintfrompackage.jsonscripts - Rust:
cargo test,cargo clippy - Go:
go test ./... - Make:
make testwhen aMakefiledefines atesttarget
doctor reports missing
optional integrations without printing credential values.
Productivity tools are supported too:
gh, railway, and vercel) when those
integrations are selected.
Repository and collaboration credentials use the same flow:
fix GitHub issues in my code. Arka routes this to the repo-scoped
coding agent, which inspects issues through gh when authenticated, reproduces
the problem, edits locally, and runs focused tests. Authenticate with
gh auth login first; Arka will not claim an issue is fixed without access or
verification.
For integrations that normally take manual setup, use the search provider
wizard. It stores keys in Arka’s user .env and supports Serper, Tavily, and
Brave Search:
--key for an interactive hidden prompt; keep --key for CI and scripts:
set up Serper,
show available integrations, or check my Sentry integration.