QA Agent for the GigaCode CLI: 14 roles and 6 skills for testing
QaAgentGigacodeCli
Requirements-based testing in GigaCode: from analysis and autotest review to a conclusion, with duplicate search before a bug is filed in Jira
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The qa-start command applies a package update from the network itself, after a CI pass check
- Roles run scripts and can create defects in Jira, so project settings should be checked before the first real run
Install
- Services
Manual install
/qa:initThe command runs in GigaCode with the QA extension connected; without it install the package manually per `docs/PROJECT_INSTALLATION.md`. Git, Python 3.10 and a network are needed.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The qa-start command applies a package update from the network itself, after a CI pass check
- Roles run scripts and can create defects in Jira, so project settings should be checked before the first real run
This is third-party code. Review the repository files before installing.
What it does
A QA package for the GigaCode CLI from GitVerse: a coordinator, 14 specialized roles (analyst, feature tester, autotest reviewer, defect investigator, Jira defect creator and others), 6 skills, verifiable result contracts and Python tools on the standard library. Roles, skills and commands go into the project `.gigacode/` folder, and the package itself lives in `.qa-agent/package/`. The `/qa:init` command downloads the source and runs the local installer, `/qa <goal>` starts the work and `/qa:doctor` checks the installation. The `qa-start` alias checks for a package update, applies a verified version and opens GigaCode. The `jira-defect-creator` skill looks for duplicates, builds a checklist and validates arguments before creating a defect. No MCP server is shipped or needed.
Who it is for. QA engineers and testers working in the GigaCode CLI who want to run testing by roles instead of one long prompt.
Good fit when
- A new feature has to be tested against requirements, from analysis to a conclusion with result review
- Defects have to be filed in Jira with duplicate search and field validation
- You need an assessment of change impact on testing and a review of autotests
- The package should be kept in Git with its profile and updated with verified versions
Not a fit when
- You need Claude Code or Cursor: the main profile is built for the GitVerse GigaCode CLI and another CLI needs its own adapter
- You need automatic Jira polling: it is not provided and the package works on request
- You need one simple skill: this is a whole system of a coordinator, roles and contracts
Example request
/qa Test the feature "orders filter by date" against the requirements from the ticket, with no external systemsLimitations
The main profile is built for the GigaCode CLI: to work in another CLI you need a compatible adapter and your own role set. Python 3.10 or newer, Git, a network and an allowed shell tool are required, on macOS, Linux or WSL. For real checks you must specify the stand, build, data and allowed actions. The model, authorization, Jira and other connections are configured separately, and secrets are not committed to Git. There is no automatic Jira polling. The target project profile for filing defects is set up by you. Version 2.3.18, zero stars, last commit in October 2026, MIT license.
How to disable. Delete the `.qa-agent/` folders and the QA roles, skills and commands from `.gigacode/`, and remove the `qa-start` alias from the shell profile.
FAQ
Is an MCP server needed?
No: a QA MCP server is not required or shipped, and all scripts live inside the project.
How do I install it?
With `/qa:init` in GigaCode with the QA extension connected or by project installation per `docs/PROJECT_INSTALLATION.md`; Git, Python 3.10 and a network are needed.
How do I update the package?
With `qa-start`: it checks for a new version, applies a verified update and launches GigaCode; `--no-update` skips the network check.
What does `jira-defect-creator` do?
It looks for duplicates, builds a summary checklist and validates arguments and the saved issue when filing a defect; the project profile is set up separately.
What tasks should I start with?
With a task from requirements and no external systems; for real checks specify the stand, build, data and allowed actions.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsProcess Kit for GigaCode
process-kit
A GigaCode workspace where the assistant takes a task in words, finds a ready process made of steps and runs it with a plan and a report in outputs
GigaCode Bridge MCP
Gigacode-bridge-mcp
MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review
The agent writes code, people decide, and gates are held by hooks in Claude Code, Codex, Cursor, OpenCode, Qwen Code and GigaCode
GigaCode project flows with hooks, gates and OpenSpec
gigacodeAgents
A monorepo of flows for the GigaCode CLI: development with stages and hard gates, a work progress observer and reverse analysis of code into a spec
Gigacode Task Commit Check
gigaide-precommit-gigacode
GigaIDE and JetBrains plugin that runs chosen GigaCode CLI tasks before a commit with the change context passed as JSON
A Python runner executes tasks from tasks.md one GigaCode iteration at a time, then five reviewers and a finalize pass, with a separate commit per task
README in short
The README describes the package contents (a coordinator, 14 roles, 6 skills, contracts, Python tools), project installation and the `/qa:init` command, the `qa-start` alias and updates, the `/qa:doctor` check, rules for first runs and defect filing through `jira-defect-creator`.