Repository navigation
Contribution and Gates
github-actions[bot] edited this page Oct 13, 2026
·
2 revisions
Contribution is governed by explicit repository gates rather than convention alone.
- Husky pre-commit and pre-push hooks.
- Commitlint / conventional commit rules.
- Strict ESLint + TypeScript.
- Unit/integration/E2E testing standards.
- Affected-workspace validation.
- Generated knowledge freshness checks.
- Architecture lint checks.
- QA-team evidence rules.
- Release preflight.
- Release notes/versioning workflow.
git add <explicit paths> → git commit (conventional subject plus a Docs: trailer) → git push. The hooks run the gates the change type needs, scoped to what changed, and CI runs the rest — a normal change runs no lint, typecheck, test or build by hand. Which gate runs for which change: the gate matrix in rules/23. Every feature or fix also carries its QA evidence record (npm run qa:evidence:new).
Sources:
ClawAI Wiki · source-controlled under wiki/ · generated/mirrored from the current repository knowledge layer.
ClawAI Wiki
Product
- Product-Vision
- Flagship-Features
- Business-Overview
- Requirements-Register
- Drift-Log
- Runtime-Managed-Connector-Providers
- Threads
- ADR-Index
Architecture
- System-at-a-Glance
- Architecture-Map
- System-Architecture
- Message-Flow
- End-to-End-Data-Flow
- Routing-Engine
- Event-Bus
- Security-Architecture
Platform
- Backend-Services
- Frontend-Architecture
- Shared-Packages
- Database-Reference
- API-Reference
- Provider-Catalog
- Memory-and-Context-Architecture
- File-Support-Architecture
- Research-and-Web-Crawling
Runtime & Ops
- Docker-Guide
- Nginx-Reference
- CI-CD-Pipeline
- Logging-and-Observability
- Operational-Runbooks
- Troubleshooting
Quality
Engineering OS
- AI-Native-Engineering-OS
- Generated-Manifests
- Rules-Catalog
- Skills-Catalog
- Context-Layer
- Engineering-Memory
- Tooling-and-Automation
- Scripts-and-Operations
- ESLint-and-Architecture-Enforcement
- Extended-Work-Skills
Agents
Reference