Different AI

Investigate failed tests, type checks, builds, and CI jobs by recording exact evidence and repeating checks in a clean comparison environment. Use the results to distinguish existing failures, newly introduced problems, environment issues, and unresolved cases.

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

• Checking whether a failing test was already broken
• Investigating a failure that appears only in CI
• Distinguishing timeouts from environment problems

Control a running OpenWork app from the shell to inspect UI changes and reproduce chat states. Start fresh sessions, select models, send prompts, wait for completion, capture screenshots, and run JavaScript, with no visible window by default.

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

• Inspecting an OpenWork UI change
• Reproducing a chat state in a fresh session
• Capturing screenshots after a model finishes

Capture UI journeys in Daytona as labeled screenshots and optional video clips. Organize them into a browsable HTML page for PR presentations, helping reviewers follow user actions and compare behavior before and after a change.

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

• Sharing UI steps through a labeled screenshot page
• Recording streaming text, loading states, or animations
• Presenting before-and-after UI behavior in a PR

Publish an OpenWork version through Git tags and GitHub Actions without creating version-update commits. Review outstanding fixes, monitor builds and publication, check release assets, and recover failed distribution steps using procedures that protect already published desktop installers.

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

• Publishing a patch, minor, or major OpenWork release
• Reviewing open fixes before creating a release tag
• Recovering distribution steps for an existing release tag

Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.

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

• Running a single end-to-end test
• Verifying the exact commit intended for a PR
• Investigating skipped tests and missing prerequisites

Introduce new users to OpenWork with explanations suited to their technical background. Cover file summaries, document creation, and organization, plus setup guidance for models, skills, plugins, and connections to external tools.

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

• Getting started with OpenWork
• Learning how to request file summaries and organization
• Understanding skills and plugins

Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.

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

• Adding custom tools to OpenWork
• Creating a plugin to save and list notes
• Running custom code before or after tool execution

Load API keys, tokens, and other secrets from Infisical into a shell or a specific command. The skill covers finding secret names, checking availability, and passing values to commands without displaying or logging them.

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

• Loading a missing API key before running a command
• Passing secrets only to the process that needs them
• Checking secret names and availability without displaying values

Read design review notes attached to a pull request’s screenshots, locate the affected components, and fix the product code using the team’s design rules. Repeat the review and inspect screenshots to verify the result.

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

• Resolving design notes on a pull request
• Reproducing reported layout problems locally
• Fixing shared components behind repeated UI issues

Create or revise pull request descriptions using a fixed template and concise language. It organizes the user problem, previous behavior, implementation, release note, and verification details so reviewers can understand the change before reading the diff.

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

• Write a concise description for a new pull request
• Shorten a lengthy pull request description
• Write a release note describing a visible user change

Attach screenshots, images, or videos to GitHub pull requests and issues using GitHub CLI. It also covers embedding images within comment text, adding alternative text, and retrieving an uploaded asset’s URL from the posted comment.

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

• Attach a screenshot to a pull request
• Add a video to an issue report
• Embed an image within a GitHub comment

Measure chat layout jumps while a response runs by tracking the Working line through CDP, a browser debugging connection. Count upward movements and compare the same prompt before and after changes to status lines, step rows, or folding behavior.

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

• Checking layout jumps after changing progress displays
• Measuring jumps caused by collapsing content
• Comparing flicker before and after a UI change

Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.

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

• Checking changes for customer and partner identities
• Reviewing documents and test data for identifying details
• Reporting disclosure locations without repeating identities

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

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

• Registering a feature before implementation
• Releasing a feature to selected organizations
• Separating cloud and self-hosted availability