review-architecture
Review architecture quality, maintainability, and developer experience.
Best use case
review-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Review architecture quality, maintainability, and developer experience.
Teams using review-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review-architecture Compares
| Feature / Agent | review-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Review architecture quality, maintainability, and developer experience.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Review Architecture You are reviewing Databao CLI architecture with NO prior context. ## Scope Review scope: $ARGUMENTS (default: `branch`) - `branch` -- architecture of code changed on current branch - `module:<path>` -- specific module - `full` -- full project architecture ## Sources of truth 1. `docs/architecture.md` 2. `docs/python-coding-guidelines.md` 3. `docs/testing-strategy.md` 4. `CLAUDE.md` 5. `README.md` ## Architecture checklist - Modules aligned with single responsibility? - CLI concerns separated from business logic? - Click command structure clean and discoverable? - `workflows/` delegates to `features/`, no business logic? - `features/` free of Click dependency? - `shared/` limited to cross-feature utilities? - MCP tools properly isolated? - Errors actionable and surfaced at right layer? ## Dev UX checklist - New contributors find entrypoints quickly? - `uv`/`make` commands obvious and consistent? - Defaults safe when deps missing? - Naming and layout reduce cognitive load? ## Output format 1. **Current State**: 3-6 bullets on what works well 2. **Risks/Gaps**: prioritized (High/Med/Low) with evidence 3. **Recommendations**: concrete, ordered by impact vs effort 4. **Doc Sync**: files needing updates 5. **Validation Plan**: commands to verify changes ## Guardrails - Small composable changes over rewrites. Tie recommendations to pain points. - Keep proposals compatible with `uv` workflow and Click CLI. - Actionable for next PR, not aspirational.
Related Skills
local-code-review
Review local code changes for correctness, regressions, missing tests, and Databao-specific risks.
write-tests
Write or update unit tests for changed code, following project conventions and ensuring coverage meets the 80% threshold.
update-pr
Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.
setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
make-yt-issue
Ensure a YouTrack issue exists before starting work. Validates existing tickets or creates new ones.
eval-skills
Run structured evaluations on skills to measure quality and track improvements.
create-pr
Stage, commit, push, and open a GitHub PR following project conventions. Use when code is ready to ship.
create-branch
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
check-pr-comments
Fetch unresolved PR review threads, triage them, implement fixes, validate, reply in-thread, and resolve.
check-coverage
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
autosteer
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
performing-serverless-function-security-review
Performing security reviews of serverless functions across AWS Lambda, Azure Functions, and GCP Cloud Functions to identify overly permissive execution roles, insecure environment variables, injection vulnerabilities, and missing runtime protections.