rust-2026-template

Generate a DORA-REPORT.md for this repository by computing the five core DORA software delivery performance metrics and three DORA agentic metrics from available data sources. Use this when asked to generate a DORA report or assess delivery performance.

Generate a human-friendly overview infographic by scanning the live project structure, including workspace crates, skills, and scripts. Use this skill whenever the user asks to regenerate, refresh, or update the overview diagram. Triggers on phrases like "update the overview", "regenerate the overview SVG", or "sync the overview".

Run comprehensive linting and static analysis on Rust code including clippy, format check, security audit, supply chain, and unused dependencies. Use before committing, during CI, or when reviewing code quality. Triggers: "lint rust", "clippy", "static analysis", "code quality".

Read all open issues (GitHub/GitLab), categorize by type and effort, plan batch implementation order, and coordinate implementation across multiple issues in a single PR/MR. Auto-detects platform from git remote. Use when asked to "implement all issues", "fix all open issues", "batch implement", or "address all issues". Triggers: "all issues", "implement all", "batch issues", "open issues", "fix all", "address all issues".

Automated secret scanning using secretlint to prevent credential leaks.

Harness engineering guide — maps all sensors and feedforward guides, teaches self-correction protocol when a CI sensor fires. Use when a sensor fires, before making code changes, or when setting up agent context for a new task. Triggers: "harness", "sensor fire", "CI failure", "self-correction".

Compile, test, and verify Rust projects following 2026 best practices. Use when asked to build, compile, or check a Rust project, when CI/CD pipeline needs build steps, or when investigating build failures. Triggers: "build rust", "compile project", "cargo build", "check rust".

Apply this skill when auditing, writing, or reviewing Rust code to avoid generic "AI slop" patterns: boilerplate structs with no purpose, copy-paste error handling, meaningless variable names, over-engineered abstractions, or hollow documentation. Triggers: "this looks AI-generated", "too much boilerplate", "meaningless names", "over-abstracted", "audit my code", "humanize this", "why is this so verbose", "remove unnecessary abstractions", "fix docs", "anti-pattern review".

Atomic git workflow - validates, commits, pushes, creates PR/MR, and verifies CI with zero-warnings policy. Orchestrates complete code submission as state machine with rollback on failure. Supports GitHub (gh) and GitLab (glab). Triggers: "commit changes", "push and create PR", "submit code", "atomic commit".

Use Codacy static analysis CLIs to query PR analysis, triage issues, suppress false positives, and run local analysis. Use when Codacy blocks a PR, when asked to fix Codacy issues, suppress false positives, query PR quality data, or integrate Codacy into CI/CD workflows. Also use when the user mentions "Codacy", "static analysis check", "code quality gate", or "Codacy is failing".

Verify that a new Rust crate name is available and appropriate on crates.io before committing to it. Use when creating a new crate, starting a new Rust project, or before the first cargo publish. Triggers: "check crate name", "is name taken", "crates.io available", "new crate".

Invoke for complex multi-step tasks requiring intelligent planning and multi-agent coordination. Use when tasks need decomposition, dependency mapping, parallel/sequential/swarm/iterative execution strategies, or coordination of multiple specialized agents with quality gates. Triggers: "complex task", "plan implementation", "multi-step", "coordinate agents".

Record agentic task completion via event files for DORA observability.

Prevent email addresses and personal data from entering the codebase. Use when user asks to "prevent emails", "remove personal data", "privacy check", "no email", or when writing/editing any Rust code, Cargo.toml, config, or documentation files. Also triggers during code review, quality gate checks, or when adding contact information.

Create and publish a new release of the Rust project. Handles version bumping, changelog, tagging, and GitHub Release creation via CI. Use when preparing a release, tagging a version, or publishing to crates.io. Triggers: "release", "publish crate", "new version", "bump version".

Self-learning fix loop - commit, push, monitor CI, auto-fix failures using swarm agents with skills on demand, loop until all checks pass. Supports GitHub Actions and GitLab CI. Use when CI fails and you need to iteratively fix until green. Triggers: "fix CI", "loop until green", "auto-fix failures", "self-fix".

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Reusable skill for evaluating other skills with structure checks, eval coverage review, and real usage spot checks. Use when you need to check a skill, add evals, benchmark a skill, validate outputs against assertions, or compare current skill behavior against a baseline.

Break down complex tasks into atomic, actionable goals with clear dependencies and success criteria. Use when planning multi-step projects, coordinating agents, or decomposing complex requests. Triggers: "break down task", "decompose", "plan steps", "task breakdown".

Run the complete test suite for a Rust project including unit tests, integration tests, doc tests, and coverage. Use nextest for parallel execution. Use when running tests, debugging failures, or checking coverage. Triggers: "run tests", "cargo test", "test suite", "coverage".

Run a systematic TRIZ contradiction audit against a Rust codebase, architecture, or workflow to identify hidden trade-offs and innovation opportunities. Use when facing design trade-offs, contradictory requirements, or needing to identify innovation opportunities through systematic contradiction analysis. Triggers: 'TRIZ audit', 'contradiction analysis', 'innovation audit', 'trade-off analysis', 'hidden trade-offs'.

Systematic problem-solving using TRIZ (Theory of Inventive Problem Solving) principles adapted for software engineering. Use when stuck on complex problems, facing technical contradictions, optimizing system design, or seeking innovative solutions beyond trial-and-error. Prevents solving the wrong problem correctly.

Verify GitHub Actions / GitLab CI action versions against actual releases before pinning. Never trust version comments — always resolve the real SHA from the upstream repository. Use when editing CI workflows, adding new actions, auditing pinned versions, or fixing version mismatches.