3.7K skills ・ Works with: GitHub · sorted by popularity
Find and fix bugs in websites, APIs, command-line tools, and background processes. Choose from three testing depths, verify fixes, and receive evidence of the changes plus a summary of readiness for release.
Review plans for APIs and developer tools through the eyes of their users. Explore developer needs, compare competitors, and identify onboarding friction, with modes for competitive differentiation, detailed refinement, or critical gaps.
Review proposed code changes before merging them. Compare changes with the base branch to find structural issues, including unsafe SQL, misplaced trust in large language model inputs, and unintended effects within conditional code.
Run sequential reviews of a plan from business, design, engineering, and developer experience perspectives. Apply six principles to intermediate decisions, then bring close choices, scope questions, and reviewer disagreements to a final approval step.
View release versions claimed by open pull requests, proposed code changes, alongside work in related Conductor workspaces. Get a read-only snapshot showing queued work and the version slot that /ship would choose next.
Use OpenAI Codex CLI to review code changes, challenge an implementation by looking for ways it could fail, or discuss technical questions. Three modes provide an independent opinion, with follow-up questions supported in ongoing consultations.
Audit a developer product by trying its documentation and setup flow, measuring onboarding time, capturing errors, and reviewing command-line help. Produce an evidence-backed scorecard and compare results with earlier planning scores when available.
Review a product or business plan from a founder’s perspective. Challenge assumptions and reconsider the problem, then explore whether to expand the scope, add selected ideas, keep it fixed, or reduce it to essentials.
Merge an existing pull request, wait for automated checks and deployment, then verify production health with canary checks, targeted checks for problems. Continue the release workflow after /ship has created the pull request.
Measure web page loading times, rendering milestones, and resource sizes in a real browser. Save baseline measurements, compare results before and after code changes, and inspect historical trends to spot performance regressions.
Review a week of engineering work using commit history, work patterns, and code quality measures. It tracks trends across retrospectives and breaks down each team member’s contributions, highlighting strengths and areas for growth.
Browse available Codex skills and install them from a curated list or a specified GitHub location. Supports experimental skills, private repositories with credentials, and installing several skill folders in one operation.
Track pull requests opened by a Paperclip instance, explain their purpose, and assess whether their latest changes are ready to merge. Dispatch preparation work for unresolved problems and publish an evidence-based report without merging anything.
Investigate failing or pending checks on the latest commit of a GitHub pull request. Reproduce actionable failures, fix and push changes, then recheck remotely until checks pass or a specific blocker is reported.
Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.
Prepare user-facing changelogs for stable Paperclip releases from commits, change records, and merged pull requests. Group related changes, identify breaking changes, and explain upgrade actions using the beta version selected for release.
Coordinate Paperclip vulnerability response from confidential report review and private fixes to local testing, CVE identifier requests, advisory publication, and immediate security releases, with human assistance for reporter communication.
Prepare completed changes for a GitHub pull request with organized commits, a clear title and description, verification evidence, screenshots for interface changes, and explicit replies to review comments through merge readiness.
Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.
Automatically gathers the past 24 hours of activity from connected services into one morning dashboard, bringing together meetings, pending replies, tasks, and development updates in visual modules suited to each type of information.
Create an HTML presentation for a community-growth campaign across GitHub, Discord, and X. Organize growth loops, a content calendar, and pipeline calculations in a coordinated cream, coral, and near-black slide design.
Summarize the past 24 hours of GitHub pull requests, review requests, issues, CI runs, and merges in a daily briefing. The GitHub-style page highlights pending reviews and failed automated checks.
Build an HTML dashboard for a public GitHub repository, showing stars, forks, contributors, issues, pull requests, and recent activity. Choose a standalone page or source files that support updates and record where the data came from.
Reproduce an existing website locally by examining source code, collecting assets, and checking browser behavior. Follow paths for static, framework-based, or graphics-heavy sites, then compare the result with the original and replace content as needed.