Jij-Inc

Append release note entries for the current PR to the relevant OMMX Python SDK and/or Rust SDK release notes

Use when deciding, auditing, or applying GitHub Release labels on OMMX pull requests, especially `rust`, `python`, `proto`, `lean`, `documentation`, `bug`, or `breaking change` labels for release-note generation from the actual PR diff.

Use when reviewing, designing, triaging, or managing OMMX benchmarks, CodSpeed runs or flamegraphs, performance PRs or issues, benchmark workload changes, or benchmark CI policy. Classify the measurement purpose, define the benchmark contract and cost model, validate the required scaling or profile evidence, assign a lifecycle and run policy, and keep CI cost proportional to the regression signal.

Use when triaging, labeling, closing, rewriting, or organizing GitHub issues in Jij-Inc/ommx, especially when deciding consistent issue labels, separating issue backlog labels from PR release-note labels, auditing open issues, or applying GitHub issue metadata changes.

Use when reviewing changes to Arbitrary implementations, proptest strategy parameters, or property-test generators in the OMMX Rust SDK, including changes to what a default strategy generates.

Use when reviewing OMMX Python SDK changes, PyO3 bindings under python/ommx/src, public Python API shape, pyo3-stub-gen output, generated stubs, Python-side wrappers, or tests for Python SDK behavior.

Use when reviewing OMMX code, PR diffs, or proposed fixes to analyze domain semantics, invariants, and responsibility boundaries before writing findings or changing code.

Use when writing or reviewing Rust module structure, item visibility, public API exposure, or pub/pub(crate)/pub(super) choices in OMMX.

Create a summary markdown file for the current branch that explains its work relative to `origin/main`. This skill uses a separate subagent or AI model to validate the summary. Keep an eye on the usage limit.

Review code on the current branch for Qamomile philosophy and convention compliance. Compares changed files against `main` and evaluates them against Qamomile's design principles.

Qamomile's mandatory cross-backend execution test policy for qamomile/circuit/algorithm/ and qamomile/circuit/stdlib/. Use whenever adding or modifying an algorithm/stdlib qkernel, or when adding a new SDK backend, so the change ships tests that actually transpile AND execute on every supported backend (Qiskit, QuriParts, CUDA-Q). Missing coverage is a P1 in /local-review.

Qamomile's mandatory Google-style docstring convention for every function, method, and class in qamomile/ (public and private alike). Use whenever writing or editing code under qamomile/ so the docstring has the required Args/Returns/Raises sections. Enforced by /local-review (missing docstrings are P2+).

docs/en/配下の英語ドキュメント(.py jupytext形式)をdocs/ja/に日本語翻訳する。翻訳ルールとワークフローを定義。

Generate Qamomile's EN/JA release notes (`docs/{en,ja}/release_notes/v<X_Y_Z>.md`) from the diff between the previous version tag and current main. Defines the section order, snippet verification, link conventions, and the related-file updates.

Simplifies and refines Python code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

This skill should be used when the user asks to solve QCoder-style quantum programming tasks, implement Qamomile kernels, debug Qamomile benchmark failures, run offline Qamomile evaluations, or build paper-derived quantum algorithm demos without web access.

This skill should be used when the user asks to solve QCoder-style quantum programming tasks, implement Qamomile kernels, debug Qamomile benchmark failures, run offline Qamomile evaluations, or build paper-derived quantum algorithm demos without web access.