
airbot-typescript
TypeScript style and testing rubrics for AIRBot reviews.
- version
- 0.1.0
Install
/plugin install airbot-typescript@airbot-reviewersRun it inside Claude Code after adding the marketplace with /plugin marketplace add sids/airbot.
Contents
Discovered from sourceSkills 2
Mission
- Ensure pull requests maintain or improve automated test coverage and reliability.
- Highlight missing regression tests, flaky patterns, or gaps in the review workflow.
When to Block
- Production code changes without corresponding tests or documented rationale.
- Failing or removed tests without replacement coverage.
- Async logic, parsers, or critical flows introduced with no deterministic assertions.
Checklist
- Identify impacted modules via diff; confirm matching updates under
tests/or a justified explanation. - Require Bun test fixtures close to their source modules; suggest new files under
tests/<area>. - Encourage fast, deterministic tests: avoid sleeping, network calls, or reliance on local environment state.
- Verify mocks and stubs cover both success and failure paths, especially around GitHub and Claude SDK interactions.
- Promote table-driven tests for parsing, dedupe, and formatting utilities.
- Ask for regression coverage when fixing a bug; tests should fail before the fix and pass after.
Tooling Tips
Readedited test files to confirm assertions exercise new code.Globfor*.test.tsnear touched modules to gauge existing coverage.Grepfor TODOs orskipcalls that might hide missing coverage.
Mission
- Enforce readable, maintainable TypeScript that matches AIRBot conventions.
- Prioritize issues that break builds, lose type safety, or harm long-term maintainability.
Quick Triage
- Block PRs for TypeScript compile errors, missing exports, or obvious runtime crashes.
- Flag high-churn files with risky refactors unless tests or migration notes exist.
- Praise meaningful improvements to typing, structure, or docs.
Style Heuristics
- Prefer explicit
typealiases or interfaces when exporting shared shapes; avoid anonymous object literals. - Require strict null handling: guard
undefinedandnull, avoid non-null assertions unless justified. - Ensure
asyncfunctions propagate errors or handle them locally; reject swallowedcatchblocks. - Favor pure utilities in
src/*modules; move orchestration or side effects tosrc/index.ts. - Keep imports sorted by module path and remove unused imports, enums, and helper functions.
- Encourage
constoverletunless mutation is necessary; avoidvar. - Recommend descriptive naming: PascalCase for types, camelCase for variables, kebab-case for files.
Type Safety
- Reject usage of
anyorunknownwithout runtime guards; suggest narrower generics or refinements. - Require exhaustive
switch/ifchains on discriminated unions; enforceneverexhaustiveness checks where practical. - Verify third-party library calls have appropriate typings, especially for Octokit and Claude SDK interactions.
- Check that new utility functions declare return types explicitly when exported.
Documentation & Comments
- Accept concise comments that explain non-obvious control flow; remove comments that restate code.
- Encourage README/CLAUDE rubric updates alongside behavior changes.
Tooling Tips
- Use
Readto inspect files,Grepfor patterns likeany, andGlobfor locating related modules or tests.
Sponsors
Details
- Marketplace
- sids/airbot
- Source
- plugins/airbot-typescript
- Author
- AIRBot Maintainers
- Category
- Community