스킬 찾기

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

Reproduce model connection failures and interrupted responses in the desktop app using a local fault server and test providers. Check error messages and retry behavior for refused connections, DNS failures, HTTP errors, stalled requests, and cut streams.

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

• Checking error messages for model connection failures
• Testing responses to rate limits and server errors
• Reproducing stalled requests and interrupted replies

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

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

Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.

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

• Connecting browser tools to a local Electron development app
• Inspecting screen state during debugging
• Entering a task in the composer and running it

Review changed test specifications for cases where broken behavior could still pass. Report concrete gaps supported by the changes and implementation, with a minimal fix and an observable condition for resolving each advisory finding.

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

• Reviewing whether changed tests prove their stated behavior
• Finding UI tests that bypass the interaction being tested
• Checking whether save tests observe newly saved data

Set up a Windows sandbox in Daytona to test OpenWork with a simulated corporate certificate authority. Check successful and broken HTTPS connections, the desktop app’s use of Windows trust, and certificate handling in runtimes it launches.

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

• Reproducing corporate certificate failures on Windows
• Checking OpenWork’s use of trusted Windows certificates
• Comparing valid and broken HTTPS certificate chains

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

Review code changes for newly introduced security issues with a plausible attack path. Produce findings for the Warden security summary, including affected lines, severity, a minimal fix, and observable conditions for confirming the issue is resolved.

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

• Checking a PR for newly introduced vulnerabilities
• Reviewing CI changes that expose secrets or write access
• Inspecting Electron changes for unsafe permissions

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

Prepares an OpenWork Cloud/Den demo on Daytona with Acme Robotics sample data. It checks service health and sign-in, keeps the sandbox active, and returns URLs and credentials ready to share with demo participants.

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

• Preparing a cloud demo with sample organization data
• Checking demo health endpoints and account sign-in
• Keeping a demo active and organizing access details

Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.

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

• Check error messages and retry progress
• Inspect text retained after an interrupted reply
• Review grouped parallel tool calls

Manage the AI models offered through OpenWork, including model additions, removals, aliases, and pricing discounts. Validate configuration consistency and trigger the GitHub workflow that refreshes models from models.dev, then report its merge or failure result.

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

• Adding or removing models offered through OpenWork
• Changing the charged price fraction for specific models
• Checking consistency between model lists and aliases

Set up the OpenWork assistant in Slack for an approved private-alpha organization using its existing app and individual account connections. Configure permissions and reply settings, link the requesting member, and verify completed answers in DMs and allowed channels.

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

• Setting up @openwork in a Slack workspace
• Linking a member's Slack and OpenWork accounts
• Configuring allowed channels and reply visibility