Skip to content
Back to skills

Codebase Analysis 2

ASecurity

Analyze codebase for existing implementations, test coverage, and code patterns. Use when checking what's already implemented, finding related code, or assessing test coverage for features.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
testingpythonbashapidatabasebackend

Works with

  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill codebase-analysis-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Codebase Analysis 2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Codebase Analysis 2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-codebase-analysis-2/badge)](https://www.skillsdirectory.com/skills/david-li0406-codebase-analysis-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: codebase-analysis
description: Analyze codebase for existing implementations, test coverage, and code patterns. Use when checking what's already implemented, finding related code, or assessing test coverage for features.
allowed-tools: Glob, Grep, Read, Bash(uv run pytest:*)
---

# Codebase Analysis

Analyze code implementations and test coverage using Glob, Grep, and Read tools.

## Search Patterns

**Find code by pattern:**
- `backend/app/**/*.py` - All Python files
- `backend/app/routes/*.py` - Route files
- `backend/app/services/**/*.py` - Service files

**Grep patterns:**
- `class.*Provider` - Provider classes
- `def test_` - Test functions
- `@router\.(get|post)` - API endpoints

## Check Implementation Status

1. Search for related keywords in codebase
2. Check route files for endpoints
3. Check service files for business logic
4. Check model files for data structures

## Test Coverage

```bash
# List tests
cd backend && uv run pytest tests/ --collect-only -q

# Run specific tests
cd backend && uv run pytest tests/test_file.py -v
cd backend && uv run pytest tests/ -k "keyword" -v
```

## Backend Structure

```
backend/app/
├── main.py           # Entry point, router registration
├── config.py         # Settings
├── database/         # Database setup
├── models/           # ORM models, Pydantic schemas
├── routes/           # API endpoints
└── services/         # Business logic
```

## Output Format

```markdown
## Implementation Analysis

### Already Implemented
- [x] Feature A - `backend/app/routes/feature.py:45`

### Test Coverage
- [x] Unit tests - `tests/test_feature.py`
- [ ] Integration tests - Not found

### Missing/Needed
- [ ] Feature C endpoint
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…