agent-ix/dev-tools
Code and Rust reviews, test-writing guidance, backporting, security audits, project scaffolding, and documentation figures.
A skill for systematically backporting bug fixes and features across specs, templates, and downstream repositories.
Review code for Agent-IX Golden Path compliance, focusing on test style, mock boundaries, implementation gaps, and code-test alignment. Dispatches by language — Python inline, Rust via rust-review, React via review-react.
Draw diagrams, charts and CSS animations for GitHub READMEs and documentation as transparent light and dark SVG pairs, with text drawn as glyph outlines so every viewer renders it identically. Use when a README or doc page needs a mechanism or flow diagram, a chart, an animated walkthrough, figures in the ix-docs style, or when a repository's docs/images figures must be regenerated or checked.
Scaffold a new repository from an Agent IX template, verify it locally, establish AGPL and content-rights controls, and create its GitHub repository privately. Use for new project or repository initialization; do not use to change an existing repository's visibility or license.
Review React components for test coverage, including unit tests and Storybook stories with requirement traceability.
Review Rust code — idiomatic-Rust conformance and repo idioms, test conventions and tracking tags, trait-seam boundaries, stub and tautology detection, panic and unsafe surface, async/blocking and lock discipline, integer conversions at wire and persistence boundaries, resource bounds, and the gates that must actually be run. Use when reviewing a Rust change or crate, or when code-review dispatches on a Cargo workspace.
Default Rust code-style idioms — error envelopes with stable codes, safety lints, async/blocking bridges, persistence-safe integer conversions, untrusted-input hardening, typed IPC, domain-identity newtypes, and the Trace: criterion-binding test convention. Use when writing or reviewing Rust in a repo that documents no idioms of its own.
Run a generic DeepSec-backed security review and remediation burndown for one or more target repositories. Use when asked to audit a repo, app area, service family, frontend/backend/client/SDK surface, infrastructure, or security-sensitive workflow with DeepSec; when asked to create local audit artifacts, GitHub security issues, checksite coverage, finding reports, spec/AC/test traceability, or a repeatable security burndown process.
Instructions for writing tests for PG Data services, likely involving database fixtures and integration tests.
Instructions for writing Python tests (pytest), including mocking, fixtures, and golden path standards.
Index to React component testing guides.
Instructions for writing TypeScript tests (Jest), including typed mocks and testing patterns.