// Run static checks and high-level validation before a production push in the Inline repo. Use when asked to run checks, verify correctness, or do pre-push/pre-release validation across server/web/admin/apple/cli/proto changes.
| name | run-checks |
| description | Run static checks and high-level validation before a production push in the Inline repo. Use when asked to run checks, verify correctness, or do pre-push/pre-release validation across server/web/admin/apple/cli/proto changes. |
Run the minimal set of static checks and targeted builds/tests based on what changed. Prefer fast, focused checks and confirm with the user before long-running steps.
Run git status -sb and git diff --name-only. Group changes by top-level area:
server/web/admin/apple/InlineKitapple/InlineUIapple/InlineIOSapple/InlineMaccli/proto/If only docs or comments changed, report that checks are optional and ask whether to skip.
If proto/ changed, run bun run generate:proto from repo root and include generated diffs.
If dependencies changed, run the relevant install/build for that stack:
bun installcargo fetch (or rely on cargo test/check)swift build in the affected package directoryRun only what maps to the touched areas.
Backend (server/):
cd server && bun run typecheckcd server && bun run lintcd server && bun test (prefer targeted tests when possible)Web (web/):
cd web && bun run typecheckcd web && bun run build only when explicitly requested or required for release validationAdmin (admin/):
cd admin && bun run typecheckCLI (cli/ or protocol changes):
cd cli && cargo test for full validationcd cli && cargo check if a fast static check is sufficientSwift packages:
cd apple/InlineKit && swift build (run swift test if tests were modified)cd apple/InlineUI && swift buildApps:
apple/InlineIOS or apple/InlineMac, do not run full app builds. Ask the user to run xcodebuild locally if needed.Summarize what ran, what passed/failed, and what was skipped with reasons. For failures, include the first actionable error and the next recommended step.
Finalize work to prepare a commit. Clean up unnecessary debug logs, remove unused methods added, do a final review to ensure tight elegant implementation, etc.
Isolate a subset of changes from a dirty local worktree (usually on main) into a clean feature branch, then commit, push, and open a PR. Use when the user asks to "branch out", "isolate my changes", "move this work to a new branch", or create a clean PR from only selected files/hunks.
Safely sync local commits with remote by rebasing onto origin/main and then push, following a GitHub Desktop-style flow. Use when asked to push/sync a branch, reconcile local and remote state, resolve rebase conflicts, run targeted tests or typechecks, and push only if checks pass.
Explain and use the Inline CLI (`inline`) for authentication, chats, users, spaces, messages, search, bots, typing, notifications, tasks, schema, attachments, downloads, JSON output, and configuration. Use when asked how to use the Inline CLI or its commands, flags, outputs, or workflows.
Guide an in-progress rebase with conflicts by summarizing each conflict and offering 3 resolution options.
Read changes, summarize spec and work done so far, and prepare for working on next steps.