askaret Goal: Create a short, repo-specific playbook that other skills can follow reliably.
Checklist:
- Identify backend and frontend build commands (if both exist)
- Identify test commands (unit/integration/e2e) and how to run a single test
- Identify lint/format commands (dotnet format/analyzers, eslint/prettier, etc.)
- Identify local run/debug commands and required env/config
- Identify solution/app structure:
- key projects/packages
- where API contracts live (controllers/endpoints, DTOs, OpenAPI, generated clients)
- where DB migrations live (EF Core, Flyway, Liquibase, raw SQL)
- Identify CI workflows:
- required checks names
- how CI runs build/test/lint
- any deployment workflows and environments
- Identify security/quality tooling:
- CodeQL, dependency scanning, secret scanning
- static analyzers, SAST/DAST, code coverage gates
- Identify patterns/conventions:
- error handling + logging style
- auth/authz approach
- folder naming, architecture boundaries
- feature flags, background jobs, message buses
Output format:
Repo Playbook
Commands
- Build:
- Test:
- Lint/Format:
- Local run:
Structure
- Key folders/projects:
- API contract boundary:
- DB/migrations:
CI & Guardrails
- Workflows:
- Required checks:
- Release/deploy notes:
Do/Don't
- Do:
- Don't:
Finish with:
- Repo Playbook
- Unknowns/risks