From repo-digest
Identify test framework, test organization, simulation methods, and test instructions. Triggered by the repo-digest command when test indicators are found.
npx claudepluginhub curryfromuestc/repo-digest --plugin repo-digestsonnetAnalyze the test and simulation setup of a repository. The prompt will contain: - `REPO_PATH`: absolute path to the repository Search for test configuration and identify the framework: | Indicator | Framework | |-----------|-----------| | `pytest.ini`, `conftest.py`, `pyproject.toml [tool.pytest]` | pytest | | `unittest` imports in test files | Python unittest | | `jest.config.js`, `jest.config...
Generates open-source packaging for projects: CLAUDE.md (Claude Code context), setup.sh (one-command bootstrap), README.md, LICENSE, CONTRIBUTING.md, GitHub issue templates. Analyzes stack and structure.
Share bugs, ideas, or general feedback.
Analyze the test and simulation setup of a repository.
The prompt will contain:
REPO_PATH: absolute path to the repositorySearch for test configuration and identify the framework:
| Indicator | Framework |
|---|---|
pytest.ini, conftest.py, pyproject.toml [tool.pytest] | pytest |
unittest imports in test files | Python unittest |
jest.config.js, jest.config.ts | Jest |
vitest.config.* | Vitest |
.mocharc.*, mocha in package.json | Mocha |
karma.conf.js | Karma |
CTestTestfile.cmake, enable_testing() | CTest |
gtest includes or TEST( macros | Google Test |
catch.hpp includes or TEST_CASE( | Catch2 |
func Test in _test.go files | Go testing |
#[test] in .rs files | Rust cargo test |
Also check package.json scripts for test commands, and Makefile for test targets.
Count test files by pattern:
test_*.py, *_test.py in tests/, test/, or anywhere*_test.cpp, *_test.c, test_*.cpp, test_*.c*.test.js, *.test.ts, *.spec.js, *.spec.ts*_test.go#[test]Estimate individual test count by grepping within test files:
def test_ and class TestTEST(, TEST_F(, TEST_P(it(, test( (not inside describe)func Test#[test]Look for simulation or benchmarking infrastructure:
File name patterns: Search for files or directories containing:
simulate, simulation, simbenchmark, bench, perfmock, fixture, fake, stubemulate, emulatorDirectory patterns: Check for dedicated directories:
benchmarks/, bench/simulation/, sim/perf/, performance/fixtures/, mocks/Content patterns: Grep for:
@pytest.mark.benchmark, timeit, cProfilebenchmark::State, BENCHMARK(performance.now(), console.time(simulate(, run_simulation(For each found simulation/benchmark method, describe:
If nothing found, state: "此仓库中未检测到仿真或基准测试方法。"
Describe how tests are organized:
.github/workflows/, .gitlab-ci.yml, Jenkinsfile)?Write step-by-step instructions to run the test suite:
Wrap all output between these exact markers. All section headers and field labels MUST be in Chinese as shown below. All descriptive text (test instructions, descriptions) MUST also be written in Chinese:
=== TEST_START ===
[测试框架]
<framework_name or "未检测到">
[测试统计]
测试文件数 : NNN
估计测试数 : NNN
[测试组织]
<description of test layout in Chinese>
[运行测试步骤]
1. <step in Chinese>
2. <step in Chinese>
...
[仿真/基准测试方法]
<description of each method in Chinese, or "此仓库中未检测到仿真或基准测试方法。">
[运行仿真/基准测试步骤]
1. <step in Chinese>
2. <step in Chinese>
...
(or "不适用 - 未检测到仿真或基准测试。")
[CI 配置]
<description of CI setup in Chinese, or "未检测到 CI 配置。">
=== TEST_END ===