Project Health Scanner
Deep dive into project health scanning and the four dimensions of analysis.
Coming Soon — Beta Waitlist Goal: 100 signups
The scanner will be available when our beta waitlist reaches 100 developers. Join the waitlist to get early access.
Overview
The Project Health Scanner analyzes your codebase across four key dimensions, providing a comprehensive health score quickly. It works with any programming language and integrates with your existing development workflow.
# Run a full project health scan
nc audit .
# Save results for tracking over time
nc audit . --save
# Verbose output with details
nc audit . -v Four Dimensions of Health
Documentation Health
Measure completeness, freshness, and cross-referencing of your project documentation.
Technical Debt
Track TODO comments, code complexity, and dependency staleness across your codebase.
Test Coverage
Analyze test file distribution, coverage gaps, and testing patterns.
Requirements Tracking
Validate requirements coverage and alignment between specs and implementation.
Documentation Health
The documentation scanner analyzes all markdown, YAML, and other documentation files in your project.
Commands
# Check documentation health
nc docs health
# Search documentation
nc docs search "authentication"
# Filter by type
nc docs search "config" --type yaml What Gets Analyzed
- • Coverage — Percentage of code with corresponding documentation
- • Freshness — How recently documents were updated vs. code changes
- • Cross-references — Broken links and orphaned documents
- • Structure — README presence, API docs, architecture docs
IDE Compatibility Checker
Score your project's AI-readiness across different IDEs and development environments.
# Check all IDE compatibility
nc test ide-compat
# Focus on specific IDE
nc test ide-compat --ide cursor
# Output as JSON for CI
nc test ide-compat --json Configuration Files Checked
VS Code
.vscode/settings.json.vscode/extensions.json.vscode/launch.json
Cursor
.cursorrules.cursorignore
Claude Code
CLAUDE.md.claude/directory
General
.editorconfigtsconfig.jsongo.mod
E2E Test Generator
Auto-generate test scaffolding for your project based on language and framework detection.
# Generate test scaffolding
nc test init
# Specify framework
nc test init --framework vitest
# Preview without creating files
nc test init --dry-run Generated Files
- •
tests/e2e/— End-to-end tests - •
tests/unit/— Unit tests - •
tests/smoke/— Smoke tests - •
.github/workflows/test.yml— CI workflow
AI Guardrails Generator
Generate safety rules for AI assistants based on your project type and connected systems.
# Generate guardrails with CLAUDE.md output
nc guardrails init --claude-md
# Override project type
nc guardrails init --type trading-bot
# Export existing guardrails
nc guardrails export --format yaml Project Type Rules
| Type | Default Safety Rules |
|---|---|
trading-bot | Verify account, check position sizes, confirm testnet/mainnet |
database | Backup before migration, verify WHERE clauses, confirm destructive ops |
infrastructure | Check dependent services, verify terraform plans, confirm resource changes |
api | Verify endpoints, check rate limits, validate auth flows |
Feature Tier Matrix
| Feature | Community | Pro | Team |
|---|---|---|---|
| Session Monitoring | ✓ | ✓ | ✓ |
| Crash Detection | ✓ | ✓ | ✓ |
| Desktop Notifications | ✓ | ✓ | ✓ |
| Project Audit | ✓ | ✓ | ✓ |
| E2E Test Generator (Basic) | ✓ | ✓ | ✓ |
| IDE Compatibility Checker | ✓ | ✓ | ✓ |
| AI Guardrails Generator | ✓ | ✓ | ✓ |
| Documentation Scanner | ✓ | ✓ | ✓ |
| Requirements YAML | ✓ | ✓ | ✓ |
| Cross-Project Intelligence | — | ✓ | ✓ |
| Pattern Learning | — | ✓ | ✓ |
| Advanced Docs Search | — | ✓ | ✓ |
| Multi-System Detection | — | ✓ | ✓ |
| Team Shared Learnings | — | — | ✓ |