cowork-mobile-app-client

Use when the user invokes $commit or asks to commit current work, make one or more git commits, split changes into logical commits, stage files or hunks, commit only selected changes, apply the repository commit message convention, or recover from a commit/staging problem. Inspect staged, unstaged, and untracked changes; preserve unrelated user work; handle merge/rebase/conflict/detached-head/no-change edge cases safely; and create title-only Korean conventional commits.

Validate changed code after work completion and before commit or PR. Use when code changes exist, before committing, or before creating a pull request to verify requirements, errors, exceptions, and available Flutter checks such as flutter analyze and flutter test; block commit/PR on validation failure.

Use when the user invokes $pr or asks to create, write, draft, update, review, or prepare a pull request title/body/description from the current branch. Inspect branch/base status, commits, diffs, PR template, and uncommitted work; coordinate with $commit when changes should be committed first; then produce a copy-ready Korean PR title and template-shaped body without inventing issue numbers, tests, or screenshots.

Analyze git diff before committing and split changes into logical commit groups. Use when git diff exists, before commits, or when changes need to be separated into feature, bug fix, refactor, configuration, documentation, test, or generated-file units without mixing unrelated work.

Create and prepare a new issue-backed work branch before starting a task. Use when a user starts a new task, asks to create an issue/branch, or there is no existing issue or work branch. Confirm the work purpose and obtain explicit user confirmation before creating any issue; then create a branch following the repo branch naming rules.

Gate actual task execution against the current issue and branch. Use when work is based on an issue/branch but implementation is forbidden or must be explicitly blocked; classify the request, prevent code implementation, and report the allowed non-implementation next steps.

Use when the user invokes $issue-work or asks to start work from an issue, create an issue branch, parse an issue, prepare a branch from develop, or begin implementation from an issue description. Inspect the issue/request, choose a branch type and kebab-case description, ensure work branches are created from develop without working directly on develop, and hand off to implementation, $commit, and $pr when requested.