Run any Skill in Manus with one click

run-checks

Stars673

Forks26

UpdatedFebruary 5, 2026 at 22:14

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

inline-chat

inline-chat/inline

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

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 Checks

Overview

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.

Workflow Decision Tree

1) Identify Scope

Run git status -sb and git diff --name-only. Group changes by top-level area:

server/
web/
admin/
apple/InlineKit
apple/InlineUI
apple/InlineIOS
apple/InlineMac
cli/
proto/

If only docs or comments changed, report that checks are optional and ask whether to skip.

2) Run Pre-Checks

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:

JS/TS: bun install
Rust: cargo fetch (or rely on cargo test/check)
Swift: swift build in the affected package directory

3) Run Component Checks

Run only what maps to the touched areas.

Backend (server/):

cd server && bun run typecheck
cd server && bun run lint
cd server && bun test (prefer targeted tests when possible)

Web (web/):

cd web && bun run typecheck
Run cd web && bun run build only when explicitly requested or required for release validation

Admin (admin/):

cd admin && bun run typecheck

CLI (cli/ or protocol changes):

cd cli && cargo test for full validation
Use cd cli && cargo check if a fast static check is sufficient

Swift packages:

cd apple/InlineKit && swift build (run swift test if tests were modified)
cd apple/InlineUI && swift build

Apps:

If changes are in apple/InlineIOS or apple/InlineMac, do not run full app builds. Ask the user to run xcodebuild locally if needed.

4) Report Results

Summarize what ran, what passed/failed, and what was skipped with reasons. For failures, include the first actionable error and the next recommended step.

More from this repository

same repository

clear-worktree

inline-chat/inline

Safely clear a dirty Inline repo worktree by inspecting uncommitted changes, classifying them as safe to commit, review-needed, blocked, or discard candidates, running focused validation, making scoped commits, and asking before destructive cleanup. Use when the user asks to clear the worktree, clean up WIP, commit what is safe, decide what needs Mo review, or update the repository-specific rules for what can be committed versus blocked.

2026-06-20673

modern-apple-frameworks

inline-chat/inline

Use when writing, reviewing, or modernizing Swift code that touches Observation, SwiftUI model data, UIKit/AppKit automatic observation tracking, SwiftUI interoperability with UIKit/AppKit, or Apple APIs gated by iOS/macOS versions. Read this before adopting @Observable, migrating ObservableObject code, using new UIKit/AppKit lifecycle tracking, adding SwiftUI to existing UIKit/AppKit apps, or checking whether an iOS 18/macOS 15 or iOS 26/macOS 26 API is safe for the current deployment target.

2026-06-19673

review-change-impact

inline-chat/inline

Review local app/code changes after implementation and produce a concise technical handoff. Use when the user asks for a review, risk assessment, tradeoff check, "what should I review", "give me snippets", or a high-level impact summary after changes that affect multiple app areas, UX, behavior, complexity, tech debt, or bug risk.

2026-06-18673

test-modernizer

inline-chat/inline

Modernize existing Swift test suites by migrating XCTest to Swift Testing or improving current Swift Testing structure. Use when asked to modernize, update, migrate, supercharge, or convert tests. Do not use for writing new tests from scratch, XCTest-only questions, test result review, test running, coverage updates for new functionality, debugging failures without a migration request, or XCUI UI automation tests.

2026-06-09673

sync-rebase-and-push

inline-chat/inline

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.

2026-02-20673

inline-cli

inline-chat/inline

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.

2026-02-18673

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 Checks

Overview

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.

Workflow Decision Tree

1) Identify Scope

Run git status -sb and git diff --name-only. Group changes by top-level area:

server/
web/
admin/
apple/InlineKit
apple/InlineUI
apple/InlineIOS
apple/InlineMac
cli/
proto/

If only docs or comments changed, report that checks are optional and ask whether to skip.

2) Run Pre-Checks

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:

JS/TS: bun install
Rust: cargo fetch (or rely on cargo test/check)
Swift: swift build in the affected package directory

3) Run Component Checks

Run only what maps to the touched areas.

Backend (server/):

cd server && bun run typecheck
cd server && bun run lint
cd server && bun test (prefer targeted tests when possible)

Web (web/):

cd web && bun run typecheck
Run cd web && bun run build only when explicitly requested or required for release validation

Admin (admin/):

cd admin && bun run typecheck

CLI (cli/ or protocol changes):

cd cli && cargo test for full validation
Use cd cli && cargo check if a fast static check is sufficient

Swift packages:

cd apple/InlineKit && swift build (run swift test if tests were modified)
cd apple/InlineUI && swift build

Apps:

If changes are in apple/InlineIOS or apple/InlineMac, do not run full app builds. Ask the user to run xcodebuild locally if needed.

4) Report Results

Summarize what ran, what passed/failed, and what was skipped with reasons. For failures, include the first actionable error and the next recommended step.