automation

Plugin automation from marketplace ataraxis in Sun-Lab-NBB/ataraxis. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• api-docs

  Applies API documentation conventions when creating or modifying Sphinx documentation files. Covers conf.py configuration, RST file structure, Doxygen/Breathe integration for C++ projects, tox build environments, and Makefile wrappers. Use when creating documentation for a new project, modifying exi

• audit-correctness

  Performs a thorough correctness audit of source code, hunting for active and latent bugs the test suite leaves uncaught and for behavior that breaks the contract the code itself states. Ranks work by test coverage and reports only findings carrying a concrete trigger and result. Use when auditing a

• audit-facts

  Performs a thorough fact-check audit of documentation against its authoritative source code, covering standalone documentation files and the docstrings and comments embedded in source code. Verifies every concrete claim and surfaces drift, contradictions, and substantive omissions with verbatim sour

• audit-performance

  Performs a thorough optimization audit of Python, C++, and C# source, hunting for untraceable numeric widths, algorithmic blowup, redundant allocation, hostile memory layout, and boundary, concurrency, and per-archetype language costs. Reports only findings whose cost is proven by execution multipli

• audit-project

  Orchestrates the four ataraxis audits in the order and concurrency their dependencies require, and merges their findings into one deduplicated report. Runs in full mode over a repository, package, or directory, or in change mode over the files a feature, bugfix, or refactor touched, where it gates t

• audit-style

  Performs a thorough style-compliance audit of source code, configuration, or documentation files against the applicable ataraxis framework style skill checklists. Walks every line in scope and reports only non-compliant findings with verbatim checklist citations. Use when auditing a Python package,

• commit

  Stages all local changes and creates style-compliant git commits, stopping before any push. Splits a change set spanning several isolatable concerns into a chain of commits, one per concern, and creates a single commit when the user asks for one. Offers to commit proactively after completing substan

• cpp-style

  Applies C++ coding conventions when writing, reviewing, or refactoring code. Covers .h, .hpp, and .cpp files, Doxygen documentation, naming, formatting, error handling, includes, file ordering, template patterns, embedded (Arduino/PlatformIO) conventions, and Python C++ extension (nanobind/scikit-bu

• csharp-style

  Applies C# coding conventions when writing, reviewing, or refactoring code. Covers .cs files, XML documentation, naming, formatting, error handling, using directives, file ordering, and Unity-specific patterns. Use when writing new C# code, modifying existing code, reviewing pull requests, or when t

• explore-codebase

  Performs in-depth codebase exploration at the start of a coding session. Builds comprehensive understanding of project structure, architecture, key components, and patterns. Use when starting a new session, when asked to understand or explore the codebase, when asked "what does this project do", whe

• explore-dependencies

  Explores installed ataraxis dependency source code to build a live API snapshot of the public classes, functions, and constants/enums each dependency exports, flagging where project code reimplements existing library functionality. Use when starting a session on a project with ataraxis dependencies,

• platformio-config

  Applies platformio.ini and library.json conventions when creating or modifying PlatformIO C++ project and library configuration files. Covers per-board environments, build flags, pinned lib_deps, library.json metadata, the lib_deps<->dependencies mirroring rule, the main.cpp export exclusion, and li

• pr

  Drafts a style-compliant pull request summary by analyzing all changes on the active branch relative to the default branch. Produces a concise, bulleted summary of the most impactful changes for the user to paste when opening the pull request, and a title as well when the branch carries more than on

• project-layout

  Applies project directory structure conventions when creating new projects, adding directories, or verifying project layout. Covers the five archetypes (Python-only, Python+C++ extension, C++ PlatformIO library, C++ PlatformIO firmware, C# Unity), common root files, environment, test, and documentat

• pyproject-style

  Applies pyproject.toml conventions when creating or modifying pyproject.toml files. Covers section ordering, metadata fields, dependency specifications, tool configurations (ruff, mypy, coverage, hatch), and classifier templates. Use when creating a new project, modifying an existing pyproject.toml,

• python-style

  Applies Python coding conventions when writing, reviewing, or refactoring code. Covers .py files, docstrings, type annotations, naming, formatting, error handling, imports, file ordering, and ataraxis library preferences. Use when writing new Python code, modifying existing code, reviewing pull requ

• readme-style

  Applies README conventions when creating or updating README.md files. Covers section ordering, writing style, standard section templates, badges, MCP server documentation, CLI documentation, and codebase cross-referencing. Use when writing a new README, updating an existing README, or when the user

• release

  Drafts style-compliant release notes by summarizing the pull requests merged since the previous release. Infers and recommends the release type (major, minor, or patch) for the user to confirm, then produces a numbered list of the most impactful changes. Includes a sibling-library compatibility stat

• skill-design

  Generates, updates, and verifies Claude Code skill files and CLAUDE.md and AGENTS.md project instructions. Covers SKILL.md structure, YAML frontmatter, formatting conventions, inter-skill relationships, scope declarations, and verification checklists. Use when creating or modifying skills, updating

• tox-config

  Applies tox.ini conventions when creating or modifying tox configuration files. Covers the mamba + uv + tox toolchain, envlist patterns, environment definitions, dependency installation strategies, environment naming, and project archetype variations (full Python, reduced Python, C++ extension, C++