tensor4all

Release a new tenferro-rs version. Use for workspace version bumps, tagging, crates.io publication in dependency order, and post-publish provenance verification. Publishing is irreversible and requires maintainer crates.io ownership. Do not use for ordinary feature or bug-fix PRs, and never publish from an unpushed or untagged commit.

Prepare a tenferro-rs bug-fix PR for existing intended behavior. Use for regression fixes, panic fixes, wrong-result fixes, compatibility fixes, related bug batches, repository-rule audit findings, same-root-cause bug sweeps, and false-positive bug reports that need source comments or source-contract tests. Do not use for new features, new public APIs, new backends, new dependencies, feature flags, or architectural changes; redirect those to issue intake.

Prepare a tenferro-rs bug-fix PR for existing intended behavior. Use for regression fixes, panic fixes, wrong-result fixes, compatibility fixes, related bug batches, repository-rule audit findings, same-root-cause bug sweeps, and false-positive bug reports that need source comments or source-contract tests. Do not use for new features, new public APIs, new backends, new dependencies, feature flags, or architectural changes; redirect those to issue intake.

Create or refine tenferro-rs GitHub issues through a step-by-step intake workflow. Use for bug reports, feature requests, design discussion issues, documentation issues, article-topic issues, and when a user proposes a new feature PR that must be redirected to an issue first. Do not use for implementation work.

Create or refine tenferro-rs GitHub issues through a step-by-step intake workflow. Use for bug reports, feature requests, design discussion issues, documentation issues, article-topic issues, and when a user proposes a new feature PR that must be redirected to an issue first. Do not use for implementation work.

Use when preparing, versioning, tagging, or publishing an omeinsum-rs crate release

Use when an omeinsum-rs pull request has review comments, local CI failures, or coverage gaps to address

Use when turning a GitHub issue for omeinsum-rs into a scoped implementation plan, branch, and pull request

Use when reviewing omeinsum-rs code changes for correctness, DRY, KISS, cohesion/coupling, CLI/HCI quality, and test quality

Implement an approved plan for Tensor4all.jl (maintainer use)

Write a feature spec or bug analysis for a Tensor4all.jl issue

Write a detailed implementation plan for an approved Tensor4all.jl spec

Use when auditing tensor4all-rs against REPOSITORY_RULES.md, AGENTS.md, README.md, public API docs, GitHub issue context, or repository-wide source risks with lightweight subagents, a single aggregated GitHub issue or issue body, and a standalone remediation PR.

Use when working in Tensor4all repositories or related Rust/Julia tensor projects and you need current shared agent rules for repository workflow, performance, numerical correctness, docs, tests, benchmarks, GPU kernels, or language bindings. Fetch/read the latest rules first, and load only the rule files relevant to the task.

Use when creating or bootstrapping a new tensor4all numerical Rust repository from template-rs