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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
Develop public equity trade pitches for portfolio managers, covering long, short, or paired positions. Explain the difference from market expectations, potential catalysts, gains and losses, risk considerations, and exit rules, while labeling assumptions and missing evidence.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)