Thanks for your interest in contributing. AutoCode is a set of markdown skill files for Claude Code — no build step, no compiled code, no runtime dependencies.
commands/ → Claude Code slash commands (user-invokable via /command-name)
agents/ → Agent role definitions (spawned by the orchestrator)
schemas/ → JSON schema for autocode.manifest.json
examples/ → Example manifests for different project types
docs/ → Documentation
tests/ → Test suite
- Fork the repo
- Edit the relevant
.mdfile incommands/oragents/ - Run
./test.shto verify nothing broke - Open a PR
- Create a new
.jsonfile inexamples/ - Include all top-level sections (use an existing example as a template)
- Run
./test.sh— it validates all examples automatically
Edit files in docs/ or README.md. The test suite checks that cross-references and links are valid.
- Commands (
commands/*.md) must have a## Steps,## Usage,## Behavior, or## Output Formatsection - Agents (
agents/*.md) should have structured sections (## Constraints,## Input,## Output,## Time Budget) - Examples (
examples/*.json) must include all sections defined in the schema - All commands start with a branded header (see any existing command for the format)
- Use consistent status indicators:
✓success,✗failure,○pending,►in-progress
Run the test suite before submitting:
./test.shThis validates JSON files, schema structure, agent/command conventions, cross-references, and link integrity. All 54+ checks must pass.
schemas/manifest.schema.jsonchanges require updating all 4 examples- Don't add runtime dependencies — AutoCode is pure skill files
- Don't add hashtags to any marketing copy