skills.rest
citum
citumOFFICIAL
Explore all skills by this author →
WebsiteGitHub

engine-behavior-reporting

Update Citum engine behavior coverage reports from integration test suites.

31|Updated Jan 28, 2026
Search Tags:#documentation#integration tests#Rust#nextest#test reporting#CI performance#engine behavior
One-click install
npx skills add https://github.com/citum/citum-core --skill engine-behavior-reporting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engine-behavior-reporting
Source: https://github.com/citum/citum-core/tree/main/.claude/skills/engine-behavior-reporting
Command: npx skills add https://github.com/citum/citum-core --skill engine-behavior-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps keep Citum’s engine behavior coverage report synchronized with the actual integration tests, so reviewers can trust what’s covered and understand what changed without reading all the Rust code.

Core Features & Use Cases

  • Scenario-to-report alignment: convert crates/citum-engine/tests/*.rs integration suites into behavior-oriented scenarios while keeping the published report in sync.
  • Human-first summaries: refine announce_behavior(...) descriptions so the report communicates observable behavior rather than implementation details.
  • Controlled publication workflow: regenerate the Markdown/HTML behavior report via the existing reporting pipeline without inflating normal PR CI time.
  • Traceable source references: ensure the report emits concise, repo-relative references like crates/citum-engine/tests/foo.rs:120-128 for auditing.

Quick Start

Use the engine-behavior-reporting skill to convert an added citum-engine integration test suite into readable behavior scenarios and regenerate the corresponding published behavior report.

Frequently Asked Questions about engine-behavior-reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Rust integration test report from nextest results?▼

Convert Rust integration test suites into behavior-oriented scenarios by refining `announce_behavior(...)` summaries to communicate observable behavior rather than implementation details in the generated report.

How do I add repo-relative source references to a Rust test coverage report?▼

Add repo-relative source references by editing the report generator script to map test binaries to exact source ranges, emitting concise paths like `crates/citum-engine/tests/foo.rs:120-128` for auditing.

Does regenerating engine behavior reports increase CI time on pull requests?▼

Regenerating engine behavior reports does not increase CI time, because the Skill uses a controlled publication workflow to update the Markdown/HTML output without inflating normal PR pipeline duration.

What's the best way to keep an engine behavior report aligned with new Rust integration tests?▼

The best way to keep an engine behavior report aligned is updating shared test helpers and the report generator script whenever expanding acceptance-style Rust integration test suites in the `citum-engine` crate.

Can I use nextest to produce human-readable test summaries for Rust acceptance scenarios?▼

Yes, you can use nextest to run Rust acceptance scenarios and refine the `announce_behavior(...)` helper output to produce human-readable summaries of observable engine behavior in the published report.

Related Skills

Explore More Software Engineering Skills→
aRustyDevaRustyDev

lang-rust-profiling-eng

Profile Rust tests with Valgrind and Callgrind via Nextest.

Community
Advanced
citumcitum
31

migration-behavior-reporting

Convert migration test suites into behavior-oriented scenarios for citum-migrate reports.

Official
Intermediate
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced