Spartan ai toolkit

Skill AravindS-Wick/aravindhan-skills/skills/spartan-ai-toolkit

Enforces quality gates (typecheck -> lint -> test -> build) and stack profiles (React, TypeScript, Go, Python) to prevent agent code degradation. Use when running build check, lint check, typecheck, or init rules.From its SKILL.md

Install

npx -y skills add AravindS-Wick/aravindhan-skills --skill spartan-ai-toolkit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

Spartan AI Toolkit Workflow

This skill acts as an engineering discipline layer to enforce strict coding standards, stack-specific rules, and multi-stage validation pipelines.

Target Triggers

/spartan
/spartan:build
/spartan:init-rules
/spartan:debug

Operational Guidelines

You must route tasks through the appropriate pipeline phase and never bypass the quality gates:

1. Stack Profile Discovery

Identify the project stack: React/TypeScript, Go, Python, Kotlin, or Java.
Load target profile rules.
Respect files matching .spartan/rules/* or project-specific coding guides.

2. The Verification Pipeline

For any feature development or bug fix, run the validation gates in sequence:

Typecheck Gate: Run compiler checks (e.g. tsc --noEmit, go build, mypy .).
Lint Gate: Run static lint analysis (e.g. eslint, golangci-lint, ruff check, spotlessCheck).
Test Gate: Run unit/integration tests (e.g. npm test, go test ./..., pytest).
Build Gate: Ensure production bundle builds successfully without warnings (e.g. npm run build, mvn clean compile).

[!WARNING] If any step in the verification pipeline fails, do not proceed or modify testing files to cheat the gate. Fix the source bug and re-run all validation steps from the beginning.

3. Debugging Loop (`/spartan:debug`)

When reproducing a bug, write a failing unit/integration test first to isolate the issue.
Apply the minimal code fix.
Re-run the verification pipeline (typecheck -> lint -> test).

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.