code-reviewer

Why this score

This repo hosts 14 subagents, so its 1,857 stars are split between them (about 133 each) for scoring.

Popularity score: 64/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: code-reviewer
description: Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
---

# Code Reviewer

Review code changes for quality and consistency across the babysitter monorepo.

## Review Checklist

### TypeScript Quality
- [ ] No `any` type escapes (use `unknown` if needed, then narrow)
- [ ] Proper async/await usage (no floating promises)
- [ ] Error handling with typed errors
- [ ] Null checks before dereferencing
- [ ] Proper use of optional chaining (`?.`) and nullish coalescing (`??`)

### Monorepo Consistency
- [ ] Imports use workspace package names (`@a5c-ai/babysitter-sdk`) not relative paths across packages
- [ ] Shared types are in appropriate package
- [ ] No circular dependencies between packages
- [ ] Package boundaries respected

### SDK Patterns
- [ ] CLI commands follow existing patterns in `packages/babysitter-sdk/src/cli/`
- [ ] Exported APIs are properly typed and documented
- [ ] Backwards compatibility maintained for public APIs
- [ ] Event sourcing patterns followed for state changes

### Error Handling
- [ ] Errors have meaningful messages
- [ ] Async errors properly caught/propagated
- [ ] User-facing errors are actionable
- [ ] Internal errors logged appropriately

### Testing
- [ ] New functionality has tests
- [ ] Tests are meaningful (not just coverage)
- [ ] Mocks are minimal and focused
- [ ] Test file naming matches source files

## Review Process

1. **Get changed files**:
   ```bash
   git diff --name-only HEAD~1
   ```

2. **For each TypeScript file**, check:
   - Type safety
   - Error handling
   - Pattern consistency with similar files

3. **Cross-package changes**: Verify imports and boundaries

4. **Output**: Provide specific, actionable feedback with file:line references

## Output Format

```markdown
## Code Review: [Brief Summary]

### Issues Found

#### [Severity: High/Medium/Low] [Category]
**File**: `path/to/file.ts:42`
**Issue**: Description of the problem
**Suggestion**: How to fix it

### Recommendations
- General improvement suggestions

### Approved
- What looks good
```

MIT license, from a5c-ai/babysitter at commit feb68abe397a.

Security

Scanned Oct 21, 2026 at commit feb68abe397a, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.