Coding standards, frameworks, refactoring, and code review (18.4K skills)
Build and test the multi-module Morphia project with Maven or its project wrapper. Compile the code, run all or selected tests, verify integration tests, or install build artifacts, including commands for working with a specific module.
Use this skill when a proposed fix adds a feature, dependency, or process. It helps identify evidence-backed removals first, protect important safeguards, and check the result before deciding whether any small addition is still needed.
When documentation, tests, or assumptions conflict with observed behavior, this skill directs you to inspect current code or data, record the concrete difference, and decide whether the implementation, the description, or both need updating.
Use this skill when technical design requirements seem to conflict. It helps name the contradiction, test whether time, space, conditions, or scale can separate the opposing states, and propose a concrete design that preserves both benefits where possible.
Use this skill to compare long-lived ideas, technologies, and practices when durability matters. It treats survival age as a clue to future longevity, while checking whether the field has changed and whether a newer option solves a necessary gap the proven choice cannot address.
Review `.R` scripts for code quality, reproducibility, domain correctness, tidyverse conventions, and professional standards. It produces a findings report while leaving source files unchanged; it does not run the code or verify numerical results.
Use this skill to check review comments, audit findings, or critiques against the actual source. It classifies each point as confirmed, refuted, or overstated, supports decisions with evidence, and helps apply verified fixes without introducing errors.
Checks the current work against quality and consistency gates, stages specific files, and creates a descriptive commit on a branch. It can push and open a pull request when requested, but it does not merge changes.
Diagnose why Claude Code asks for tool approval by checking permission settings and their precedence across repository and session layers. The read-only workflow starts with project-local files; it accesses host-wide settings only after explicit user confirmation.
Assess the impact of a change to a shared interface, setting, or data format by finding every consumer and running representative end-to-end paths. Compare prior outputs to catch broken assumptions, unexpected result changes, and downstream work that needs rebuilding or repinning.
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.
Push the current branch to its configured remote and create a pull request if one is missing, or update the open request to match the branch’s full scope. It checks changes and handles sync problems through the related pull workflow.
Guide a pull request through conflict checks, reviewer feedback, and CI results, fixing issues and waiting for required checks to finish. When the PR is ready, squash-merge it using its title and description.
Update the current feature branch with the latest `origin/main` using a merge, then guide conflict resolution by comparing each side’s intent. It includes steps for checking repository state, handling conflicts carefully, and reviewing the completed merge.
Continue an engineering specification from its progress table by carrying out the next planning, implementation, or review step in the current session. It follows the spec’s named model and pauses at its decision gates.
Debug Borg behavior inside a running Docker container by executing real Borg 1 and Borg 2 commands and inspecting their output. Use the results to write accurate code, tests, and error handling based on actual command responses.
Review a GitHub pull request through several focused code analysis angles, then verify and rank candidate findings. The workflow filters for well-supported, significant issues and produces actionable review feedback; it is intended for GitHub PRs, not local uncommitted changes.
Use this skill to shape a feature, component, or system before implementation. It asks focused questions, compares design options, and helps produce an agreed specification so the work starts with clearer requirements and decisions.
Handle a GitHub issue through a structured workflow: inspect its details, research related code and pull requests, plan and implement a fix, run tests, then submit a pull request that references the issue.
Create or revise agent skills, then test how they perform on realistic prompts. Review outputs and benchmark results, use feedback to refine the skill, and improve its description so agents can recognize when to use it.
Use this skill for a focused, challenging interview about a proposal or design. It asks one question at a time, tests assumptions against concrete scenarios and code, and records agreed terms and significant decisions in project context files and ADRs.
Delegate coding, code review, and implementation plan review to the OpenAI Codex CLI. Choose a sandbox level for the task, then relay Codex’s findings or implementation results; review findings are presented for the user to decide on.
Review a completed feature, work session, or incident using concrete evidence such as failed checks and rework. Identify costly friction, trace likely causes, and propose durable fixes, prioritizing automation and keeping only a few high-impact findings.
Plan and guide structural refactors across files or modules while preserving behavior and public contracts. The skill maps dependencies and consumers, ranks changes by priority, and lays out staged moves with validation steps and compatibility considerations.