OpenAI

Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.

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

• Release a specified Symphony version
• Prepare the next patch release
• Tag the merged release commit

Investigate stalled, retrying, or failed Symphony runs by connecting Linear issue identifiers with Codex sessions. Trace log events in time order, identify the failing stage, and collect evidence for the probable cause.

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

• Investigate a stalled run
• Trace repeated retries
• Identify where a Codex session failed

Publish the current Git branch to origin and create or update its pull request, a request to review and merge changes. The skill runs validation and refreshes the title and description to match the full scope.

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

• Publish local branch changes to origin
• Create a pull request using the project template
• Refresh a pull request after its scope changes

Create a Git commit from current changes using the session history to explain their purpose. The skill checks which files belong, stages the intended work, and writes a structured message covering changes, rationale, and validation.

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

• Commit completed work with its rationale
• Draft a commit message from the session history
• Check staged files for unrelated changes

Guide a pull request through conflict resolution, review feedback, and automated checks. The skill monitors progress, fixes failures, and completes a squash merge, combining the branch’s changes into one commit once checks and reviews are addressed.

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

• Follow a pull request through to its merge
• Resolve conflicts with main before merging
• Investigate failed automated checks and rerun them

Work with Linear issues through Symphony’s authenticated client. Retrieve issue details, update workflow states, create or edit comments, link GitHub pull requests, and upload videos using GraphQL, an API language for requesting specific data.

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

• Retrieve Linear issue details
• Create or edit issue comments
• Change an issue's workflow state

Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.

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

• Bring the latest main changes into a feature branch
• Resolve conflicts while preserving both changes’ intent
• Sync remote feature branch updates before merging

Read existing findings, reports, recorded assignments, verification results, and scan status from a connected Codex Security Cloud account. Summarize available evidence and distinguish missing information from confirmed outcomes without changing Cloud data.

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

• Inspect a finding from its Cloud link
• List findings by severity or recorded assignee
• Review saved validation and patch check reports

Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.

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

• Create issues from validated security findings
• Find and reuse existing issues for the same finding
• Register a reviewed batch of security issues

Assess candidate security findings using focused reproduction, tests, or code tracing. Record the evidence, confidence, and remaining proof gaps for each candidate, helping determine which findings warrant reporting and which remain uncertain.

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

• Verify whether a suspected vulnerability can be reproduced
• Reassess a finding previously marked as a false positive
• Trace vulnerable paths when runtime services are unavailable

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

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

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

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

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Create, update, or reuse a repository threat model: a document describing its architecture, attacker capabilities, trust boundaries, and potential security failures. The result is a Markdown reference grounded in the repository's actual code and scope.

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

• Documenting architecture and trust boundaries
• Creating or updating a repository threat model
• Preparing a threat model for a specific security review

Turn vulnerability notes, proof-of-concept code, source code, or security findings into self-contained reports. The skill checks claims against evidence, explains prerequisites and demonstrated impact, and supports both individual vulnerabilities and collections of disclosure reports.

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

• Turning vulnerability notes into a disclosure report
• Checking source code and proof-of-concept claims
• Preparing separate reports for multiple vulnerabilities

Run repeated, independent security reviews of an entire repository or a selected directory. The skill combines validated findings and coverage records into a final report, helping reduce variation between individual reviews.

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

• Reviewing an entire repository through repeated security audits
• Running an intensive review of a selected directory
• Combining validated findings and coverage into one report

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

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

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Audit an entire repository or a selected folder, package, or path in one review pass. Produce a security report with source evidence, severity assessments, and clear coverage limits, including unresolved questions that need further investigation.

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

• Run a standard security audit of a repository
• Review a selected folder or package
• Check findings alongside evidence and coverage gaps

Assess a fixed patch or pull request diff before merging. Trace affected behavior, evaluate regression risks, tests, and recovery options, then provide an evidence-based recommendation and advisory automatic-merge eligibility without modifying or merging the patch.

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

• Assess a generated patch before merging
• Trace how a pull request affects production behavior
• Evaluate tests and rollback options

Create or review SECURITY.md guidance so Codex Security understands what to examine, which protections must hold, and what is excluded. Compare existing policies with repository evidence and preview proposed changes before writing.

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

• Define security review scope for a repository
• Document required security protections
• Check whether existing guidance matches the code

Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.

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

• Verify remediation of a reported vulnerability
• Check for bypasses around a security fix
• Verify a fix after code moves or refactoring

Review pull requests, commits, branch differences, or local patches for security vulnerabilities. Inspect changed and deleted text files, trace relevant supporting code, and return validated findings, review comments, and a report describing coverage gaps.

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

• Review a pull request for security vulnerabilities
• Check a commit or branch diff before merging
• Inspect local changes, including deleted files

Inspect repository code or code changes for plausible security vulnerabilities. The skill records candidate issues with affected locations, attacker-controlled inputs, failing safeguards, and possible impact, preserving the evidence needed for later validation.

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

• Finding security issues that may arise from code changes
• Investigating vulnerability candidates in repository code
• Organizing source evidence for later validation

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

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

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Set up NemoClaw, create an isolated sandbox for OpenClaw, and start the first agent conversation in a browser or terminal. Follow onboarding for model connections, optional search and messaging, and network policy settings.

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

• Install NemoClaw and create the first sandbox
• Configure a model connection during onboarding
• Prepare Windows with WSL 2 and Docker Desktop