القائمة
Use when preparing a new crate release, bumping versions, or tagging a release
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you want to take a Backlog issue all the way to Final review without manual orchestration — chains check-issue, fix-issue, add-model/add-rule, run-pipeline, and review-pipeline; substantive issue-quality problems are sent to a rewrite subagent; algorithmically unsalvageable issues are parked on OnHold
Use when reviewing a [Rule] or [Model] GitHub issue for quality before implementation — checks usefulness, non-triviality, correctness of literature claims, and writing quality
Use when a user wants to propose a new problem model or reduction rule — guides them through brainstorming, clarifies the design, and files a GitHub issue
Review the Typst paper (docs/paper/reductions.typ) for quality issues — evaluates 10 entries per session, reports mechanical and critical issues without fixing
Reverse of find-solver — given a solver for a model, discover what other problems it can handle via incoming reductions, ranked by effective complexity
Interactive guide — match a real-world problem to a library model, explore reduction paths, recommend solvers (built-in + external), and generate a solution doc
| name | release |
| description | Use when preparing a new crate release, bumping versions, or tagging a release |
Guide for creating a new release of problemreductions.
Compare against the last release tag:
git tag -l 'v0.*' | sort -V # find latest tag
git log <last-tag>..HEAD --oneline # review commits
git diff <last-tag>..HEAD --stat # review scope
Apply semver for 0.x (pre-1.0):
make test clippy
Both must pass with zero warnings before proceeding.
make release V=x.y.z
This target bumps versions in Cargo.toml, problemreductions-macros/Cargo.toml, and problemreductions-cli/Cargo.toml, runs cargo check, commits, tags, and pushes. CI publishes all three crates to crates.io.