一键导入
write-tests
Write tests for the current changeset
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Write tests for the current changeset
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Update CHANGELOG.md with recent changes following Keep a Changelog format
Prepare and publish a new crate release
Format code according to specified style guide
Write Architecture Decision Records (ADRs) and technical documentation. Use when documenting design decisions, architectural choices, or technical specifications.
Senior Rust code reviewer. Use proactively after implementing features to review for correctness, safety, performance, and best practices.
Analyze Rust dependencies for security, quality, and maintenance status. Use proactively to audit Cargo.toml, check for outdated crates, or evaluate new dependencies.
| name | write-tests |
| description | Write tests for the current changeset |
Current changes to write tests for:
!jj show
Review the current changes and write tests following docs/development/testing.md and docs/development/code-style.md.
Validate your work using mise run test and ensure all code is properly formatted using mise run format.
No inline comments - Tests should be self-documenting through clear variable names and structure.
Setup + space + assertion - Separate setup from assertions with a blank line:
#[test]
fn it_does_a_thing() {
let foo = "foo";
let bar = "bar";
assert_ne!(foo, bar);
}
#[test]
fn multiple_assertions() {
let foo = "foo";
let bar = "bar";
assert_ne!(foo, bar);
let baz = "baz";
assert_ne!(foo, baz);
}
When a test has multiple logical steps, separate each setup+assertion group with a blank line.