'architecture-review' 검색 결과

Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find game requirements without architecture decisions
• Check for conflicts between architecture decisions
• Review compatibility with the pinned engine version

Review a repository’s architecture using Ontoly Software Graph, a map of code relationships. Explain module boundaries, package structure, dependencies, and architectural risks, with graph evidence and a stated confidence level.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding a repository’s overall architecture
• Reviewing module boundaries and package structure
• Investigating dependency cycles and architectural risks

Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

Review tutti git diffs for project structure, layering, module ownership, and duplicate event-center infrastructure by planning focused architecture review tasks, then having the main agent orchestrate sub-agents for only the changed areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a durable Architecture Review Record from a confirmed System Architecture Reviewer scope, evidence, pillar analysis, trade-offs, and dispositions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Survey the codebase, pick ONE high-leverage deepening opportunity (filtering out anything already proposed), and publish it as a PRD-shaped GitHub issue via /to-prd-project. Designed to run unattended in the daily architecture-review workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review recommendation-system code, architecture, experiment, or design for correctness, serving safety, offline-online consistency, capacity, observability, and rollback gaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working through architectural flaws documented in a paad/architecture-reviews/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run /agentic-architecture first if there isn't one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Architecture review and design validation. Evaluates system designs against best practices, identifies anti-patterns, and ensures architectural decisions align with non-functional requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when surfacing architectural friction and proposing deepening refactors (shallow modules → deep modules) for testability and AI-navigability. Triggers on "improve architecture", "find deepening opportunities", "where is this codebase shallow", "architecture review". Emits structured candidates + precise patches; delegates ALL rendering to mk:preview. NOT for diagram/HTML rendering (see mk:preview); NOT for trade-off deliberation (see mk:party); NOT for plan critique (see mk:plan-ceo-review).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when critiquing a system design across correctness, scalability, reliability, maintainability, and observability using probe-first questioning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a change for architectural drift, guardrail weakening, and ADR impact before shipping.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.