القائمة
Validate the chaotic_semantic_memory crate: compile, test, lint, LOC caps, and benchmarks. Use when asked to validate, check, or verify the build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | testing-validation |
| description | Validate the chaotic_semantic_memory crate: compile, test, lint, LOC caps, and benchmarks. Use when asked to validate, check, or verify the build. |
Run scripts/validate.sh for the full gate sequence.
# Minimal output mode (2026 best practice)
export CARGO_TERM_PROGRESS_WHEN=never
cargo check --message-format=short
cargo test --all-features --quiet # or: cargo nextest run --all-features
cargo fmt --check
cargo clippy -- -D warnings
Then check LOC limits with scripts/loc-check.sh.
# First run: save a baseline
cargo bench --bench benchmark -- --save-baseline main
# Subsequent runs: compare against baseline
cargo bench --bench benchmark -- --baseline main
Do NOT use cargo bench -- --baseline without a name — it fails silently.
| Layer | Location | What to test |
|---|---|---|
| Unit | src/*.rs #[cfg(test)] | Core logic, edge cases, error paths |
| Integration | tests/*.rs | Public API behavior, persistence roundtrips |
| Benchmarks | benches/benchmark.rs | Performance targets (reservoir_step < 100μs @ 50k) |
Run tests by file:
cargo test --test <test_name>
Use separate test files in tests/ for:
Every file in src/*.rs must be ≤ 500 lines. Run scripts/loc-check.sh to verify.
Run scripts/check-docs-links.sh to validate:
@file.md and [text](./path.md) style)--check-urls flag)./scripts/check-docs-links.sh # Quick check (no URL validation)
./scripts/check-docs-links.sh --fix # Auto-fix version mismatches
./scripts/check-docs-links.sh --check-urls # Full check with URL validation
new_seeded(..., 42) for determinism — don't use new() in tests.tempfile::NamedTempFile for DB path.GOAP-based orchestrator for managing GitHub issues, creating action plans, and executing workspace operations with branch/PR workflow.
Configure and troubleshoot npm OIDC Trusted Publishing for GitHub Actions. Use when npm publish fails with E404, OIDC errors, or provenance issues.
GitHub release management, crates.io trusted publishing, npm provenance, and GitHub Pages documentation. Use when creating releases, publishing packages, or deploying docs.
Git commit conventions, validation gates, and CI/CD workflows. Use when committing changes, verifying gates, or working with GitHub Actions.
Validate merge readiness with atomic commits and GitHub Actions checks using gh CLI; use for pre-merge verification and CI truth validation.
Apply TRIZ inventive principles to solve problems that seem to have no good solution. Use after triz-analysis has identified contradictions.