soil-report
Summarises a repository's test-runner configuration (framework, config file, coverage threshold) in one paragraph. Use when the user asks "how are tests configured here" or "which test framework does this repo use".
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- soil-report
- description
- Summarises a repository's test-runner configuration (framework, config file, coverage threshold) in one paragraph. Use when the user asks "how are tests configured here" or "which test framework does this repo use".
03 SKILL.md 正文
soil-report
Describe the repository's test setup in one paragraph.
Steps
- Detect the framework from config files:
pytest.ini,pyproject.toml [tool.pytest],jest.config.*,vitest.config.*,Cargo.toml. - Read the coverage threshold from the same file, if one is set.
- Write one paragraph naming the framework, the config file path, and the threshold (or "no threshold set").
Output
Tests run under pytest (config: pyproject.toml). Coverage threshold: 85%.
If no framework is detected, return exactly: No test framework configuration found.
04 同仓库更多 Skills
toy-check
A skill that checks things in the repository and reports what it finds.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
demo-check
Reports which generated files changed since the last generation run. Use when the user asks what drifted. Read-only; never edits a file.
zirkel-verify-assumptions
Checks exactly ONE named assumption against real evidence in at most 3 steps and reports one outcome: confidence raised (>=90), reading changed, or still unresolved. Use to resolve a single load-bearing uncertainty — typically a blocking entry surfaced by zirkel-clarify-scope: "verify this one assumption", "is it actually true that X", "check this before we rely on it". For multiple uncertainties, invoke once per uncertainty — the step budget is never shared.