Review code changes against project architecture, style, and conventions
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Review the current changes against the project's conventions and architecture rules.
Load the appropriate docs based on which code area is being reviewed:
@docs/store-compose.md, @docs/store-viewmodel-patterns.md, @docs/store-tracking-events.md, @docs/store-testing.md@docs/pos-architecture.md, @docs/pos-tracking-events.md, @docs/pos-testing.md@docs/coding-style.mdDetermine the diff to review. First check git diff trunk...HEAD for branch changes (most common: pre-PR review). If empty, fall back to git diff --cached for staged changes, then git diff for unstaged changes.
Determine if the code is POS or store. POS: ui/woopos/, WooPos* prefix. Everything else: store management. Read the relevant docs above.
Read the changed files in full to understand context, not just the diff hunks.
Check against each category below. Only report actual issues found — do not report categories with no issues.
ViewModel(), use parent-child SharedFlow event bus, pure Compose, Compose NavigationScopedViewModel, use triggerEvent() / MultiLiveEvent, Compose inside Fragments, XML nav graphs@HiltViewModel + @Inject constructor, data flows through repositories, ViewModels never access Room/network directlyFIXME (use TODO), no !! force unwrapsUPPER_SNAKE_CASE, companion objects at bottomdocs/store-compose.md (store) or docs/pos-architecture.md (POS)BaseUnitTest, testBlocking, captureValues, AssertJWooPosCoroutineTestRule, runTest, advanceUntilIdle, AssertJAnalyticsEvent enum, AnalyticsTrackerWrapperWooPosAnalyticsEvent sealed class, WooPosAnalyticsTracker## Blockers
- [file:line] Description of blocking issue
## Suggestions
- [file:line] Description of improvement suggestion
## Positives
- Description of what was done well
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Repair a failing WooCommerce Android Maestro flow by reproducing it against the store it runs on, inspecting Maestro selectors, patching the smallest selector/wait/setup issue, and rerunning with repeat evidence. Human-triggered only.
中文简介正在准备中。当前显示原文说明。
POS (Point of Sale) architecture and patterns. Use when writing, editing, exploring, debugging, fixing bugs, implementing features, or reviewing WooPos-prefixed classes or files under ui/woopos/. POS uses a different architecture than the main app — plain ViewModel (not ScopedViewModel), pure Compose (no Fragments), Compose Navigation (no nav graphs), parent-child SharedFlow event bus. Loading this skill prevents applying main-app patterns that would be wrong for POS. For analytics use `pos-analytics`, for tests use `pos-tests`.
中文简介正在准备中。当前显示原文说明。
POS analytics tracking patterns (WooPosAnalyticsEvent sealed class, WooPosAnalyticsTracker, WooPosAnalyticsEventConstant). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in POS (WooPos*) code. NOT for main store app — use the `store-analytics` skill instead.
中文简介正在准备中。当前显示原文说明。
POS unit testing patterns (WooPosCoroutineTestRule, runTest, advanceUntilIdle, mockito-kotlin, event bus mocking, analytics verification). Use when writing, editing, exploring, debugging, or reviewing unit tests for POS (WooPos*) code. NOT for main store app tests — use the `store-tests` skill instead.
中文简介正在准备中。当前显示原文说明。
Create a pull request following project conventions. Triggers on any request to create, open, make, submit, file, send, push, spin up, put up, draft, raise, or prepare a PR/pull request.
中文简介正在准备中。当前显示原文说明。
Address PR reviewer feedback by evaluating comments, proposing fixes, and executing after user approval. Use when the user wants to handle review comments on an existing PR, address PR feedback, fix PR comments, respond to reviewer suggestions, or process code review feedback. Triggers on "address PR feedback", "handle review comments", "fix PR comments", "respond to PR review", "process reviewer feedback", or when given a PR number/URL with intent to address its comments.
中文简介正在准备中。当前显示原文说明。