Owns the end-to-end modelcontextprotocol/csharp-sdk release process, orchestrating the prepare-release and publish-release skills (and the bump-version and breaking-changes skills they build on) across five stages: prepare (assess SemVer, bump the version, run ApiCompat/ApiDiff, review docs, draft release notes, open…
The official Linux package supplies the complete application runtime and bundled commands. There is no repository-owned runtime replacement layer. The packaged desktop entry is ChatGPT Community; codex-desktop remains the package, executable, and installation-path identity.
Agent "git-workflow" from callstack/react-native-testing-library, covering git, releases, and pr workflow, agent git restrictions, commits and releases and pr draft workflow.
acpx grok-build launches the installed grok CLI through its ACP stdio entrypoint. Install Grok Build and complete its normal authentication flow before using it through acpx.
A read-only auditor that checks whether code changes are accompanied by tests covering the changed areas. It examines the difference between two code versions and reports missing test work.
Headless variant of shelf-security-reviewer for the pre-commit hook. Receives the staged diff inline (the wrapper script pre-computes it). Tools restricted to Skill only — no Bash, no WebFetch, no Agent — so prompt injection in the diff cannot exfiltrate. Outputs a strict JSON envelope for safe parsing. Do NOT invoke…
Security-focused reviewer for Shelf PRs and diffs. Use proactively whenever the user asks to review a pull request, audit a branch, or assess the security impact of a change. Always invokes the security-review, oauth-oidc-misconfiguration, supabase, and two-factor-authentication-best-practices skills, and layers…
Hostile logic reviewer. Use after code changes to adversarially check the staged git diff for off-by-one errors, wrong algorithms, missing edge cases, bad state transitions, and dead code. Reports a minimal triggering input per finding.
Hostile maintainability reviewer. Use after code changes to adversarially scan the staged git diff for oversized functions, magic numbers, duplicated code, unclear names, and tests that don't verify what they claim. Quotes the exact offending lines.
Hostile security reviewer. Use after code changes to adversarially audit the staged git diff for injection, auth bypass, hardcoded secrets, race conditions, and information leakage. Reports severity and a concrete exploit per finding.
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when…
Use this agent when you need to resolve git merge conflicts, merge branches, or handle complex git operations involving branch integration. This includes resolving conflicts in files, choosing between conflicting changes, merging feature branches into main/master, rebasing branches, or cleaning up merge-related…
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
Use this agent when the user asks to enforce code style, find and fix analyzer diagnostics, run a full cleanup sweep, format changed files, or prepare a branch for merge by driving warnings to zero. Trigger phrases include: 'enforce code style' 'fix all analyzer warnings' 'run a full cleanup sweep' 'drive warnings to…
Checks whether a change has left generated files, doc tool-counts, or attribution stale relative to their sources. Use before calling a change done when it touched AGENTS.md, docs/, src/server.py's tool registration, apitruth.py, or the control panel — the same family of checks npm-publish runs before every release…
An agent focused on releasing software and undoing releases when needed. It also covers checks that confirm a release is healthy and coordination around database changes.
Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.
Evaluates an incoming external/contributor PR for merge readiness. Use when a contributor opens a PR, or when the user says "review PR #N", "evaluate this PR", "is this mergeable?", "이 PR 봐줘/머지 가능?". Produces a merge-readiness verdict (READY / NEEDS-CHANGES / NEEDS-DISCUSSION), a code-quality findings table, and a…
Generate a complete VIOS multi-arch release note for a given build drop version. Fetches container images from GitLab compose.env files, commit titles from GitLab between the previous release tag and HEAD, Jira VST tickets, NVBugs entries, Slack channel evidence, and Outlook email evidence, then renders a formatted…