discover-qa-tools
Discover project-specific QA tools from CI configs and build files. Use when starting a QA workflow to identify formatting, linting, and testing commands available in the project.
- License 许可
- MIT
- 所属仓库
- jbrinkman/kairon
- 最近更新
- 2026-11-06
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- discover-qa-tools
- description
- Discover project-specific QA tools from CI configs and build files. Use when starting a QA workflow to identify formatting, linting, and testing commands available in the project.
03 SKILL.md 正文
Discover QA Tools
Discover all quality assurance commands available in the current project by examining CI/CD configuration and build tool files.
Process
-
Check CI/CD configuration files for quality-related steps:
.github/workflows/*.yml,.github/workflows/*.yaml.gitlab-ci.ymlJenkinsfile.circleci/config.yml
-
Check build tool configuration for quality-related tasks/scripts:
Taskfile.yml(task names and commands)Makefile(target names)package.json(scripts section)pyproject.toml(tool sections)tox.ini(environments)
-
Extract commands that perform:
- Formatting checks (check-only/verify mode)
- Linting / static analysis
- Testing (unit, integration)
- Type checking
-
Map to local equivalents: CI commands should be mapped to locally runnable commands. Prefer build tool wrappers (e.g.,
task lint) over raw commands when available.
Output Format
Write the discovery results to .kairon/artifacts/qa-tools.md:
# QA Tools Discovery
**Project**: [repo name]
**Discovered**: [timestamp]
## Formatting Checks
- `[command]` — [source file where found]
## Linting Checks
- `[command]` — [source file where found]
## Tests
- `[command]` — [source file where found]
## All QA Commands (execution order)
1. `[formatting command]`
2. `[linting command]`
3. `[test command]`
Caching
The output file at .kairon/artifacts/qa-tools.md serves as a cache. It should be regenerated if:
- The file does not exist
- The file is older than 24 hours
- CI configuration files have been modified since the last discovery
Usage
Krew-lead invokes this skill once before the QA loop and passes the resulting command list to both builder and validator agents as context.
04 同仓库更多 Skills
selftest-conventions
Self-test override hook supplied by a case workspace fixture.
engine-skill
Engine skill for the audit fixtures.
demo-conventions
暂无简介
sentinel-protocol
Core Kairon completion-signalling protocol. Defines the sentinel file path format and write rules that every pipeline agent uses to signal task completion to krew-lead, and that krew-lead uses to detect it. This is engine behavior, not a project convention — do not override it per project.
planner-shared
Kairon-managed contract shared by both planner agents. Defines the restrictions, the stage-output document the planner returns, how to investigate and classify a request, the issue-body standard and the hard bars.
validator-conventions
Structured templates and patterns for strict criterion-by-criterion validation. Enforces exact specification compliance and provides copy-paste report templates.