396 skills ・ Works with: GitLab · sorted by popularity
Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.
Prepare code changes for sharing by merging the base branch, running tests, and reviewing the diff. Update VERSION and CHANGELOG, then commit, push, and create a pull request, a proposal to merge the changes.
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.
Create missing documentation for a feature, module, or whole project. Use Diataxis, a framework that separates tutorials, practical guides, reference information, and explanations, to organize documents around what readers need to learn or accomplish.
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.
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.
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.
Monitor a live app after deployment for console errors, slower performance, and page failures. Periodic screenshots and comparisons with pre-deployment baselines help identify anomalies and check whether the release is behaving as expected.
Review a UI/UX plan before implementation, score its design dimensions, and identify missing decisions. Through discussion, the skill adds concrete improvements directly to the plan so the review produces an updated plan.
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.
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.
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.
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.
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.
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.
Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.
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.
Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.
Design CI/CD pipelines that move applications through development, staging, and production. Define approval and security checks, gradual release strategies, health checks, and rollback procedures, and investigate gates or deployments that fail to progress.
Manage API keys, passwords, and certificates used in CI/CD, the automated process for testing and deploying software. Connect secret stores, plan credential rotation, restrict access, and prevent sensitive values from appearing in logs.
Create GitHub Actions workflows to automate testing, builds, and deployments. Includes patterns for Docker image publishing, Kubernetes deployment, security scans, and testing across multiple environments, plus reusable workflows and approval steps for production releases.
Build GitLab workflows that automate building, testing, and deployment. The skill covers pipeline stages, dependency caching, runners that execute jobs, and manual approval before production deployment, with examples for Docker, Kubernetes, and Terraform.
Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.
Convert plain text documents into Markdown while preserving their content. Follow supplied formatting rules or a reference file, organize headings, lists, and code blocks, and clean up spacing for the chosen publishing platform.