77 skills · sorted by relevance
Use Stratus Red Team to simulate attack techniques across AWS, Azure, GCP, and Kubernetes. Prepare test resources, run and repeat simulations, check logs and alerts, and remove resources to assess whether security detections work.
Prepare a deployment checklist covering tests, approvals, database changes, release steps, and monitoring. Tailor it to the release and document rollback triggers, the conditions for reverting a change, before production deployment begins.
Improve an existing skill by checking its structure and category requirements, proposing focused fixes, and testing again. Compare failure and warning counts to decide whether to keep changes or restore the previous content.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.
Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.
Apply staged skill improvements selected by the user after a fresh review of the actual changes. It backs up target files, applies passing patches, and records review evidence and change history for later inspection or reversal.
Integrate GSAP animations into React and Next.js components using useGSAP, element references, and scoped selectors. The skill guides dependency updates, event callbacks, and cleanup when components unmount, while keeping animation code out of server rendering.
Import FBX 3D models into CARLA on UE 5.8 and register them as props that can be placed in a simulation. Check measured dimensions, adjust scale, verify placement on a running server, and undo imports when needed.
Prepare a deployment checklist covering tests, approvals, database changes, release steps, and monitoring. Tailor it to the release and document rollback triggers, the conditions for reverting a change, before production deployment begins.
Investigate why TypeScript uses a particular built-in type by tracing issues, proposed changes, and team comments. Produces a linked timeline and explanation of past trade-offs to help assess type overrides in ts-reset or proposed typing changes.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
Restore project files from a previous Git checkpoint after previewing affected files and receiving explicit confirmation. Create a safety tag before restoration, preserve recorded lessons, and keep the current branch and commit history in place.
Run repeated, measured Git experiments toward a numeric target; keep improvements and revert failures. Use for autonomous optimization or managing an autoresearch run, not one-shot edits.
The English summary is being prepared. Showing the original description.
Git-aware undo by logical work unit (track, phase, or task)
The English summary is being prepared. Showing the original description.
Quantify homologous recombination deficiency (HRD) from tumor copy number using the three genomic-scar metrics — loss of heterozygosity (LOH), large-scale state transitions (LST), and telomeric allelic imbalance (TAI) — with scarHRD, and via the whole-genome HRDetect and CHORD models. Covers the genomic instability score, the PARP-inhibitor clinical context, whole-genome-doubling correction, and the scar-versus-state distinction. Use when computing an HRD score for PARP-inhibitor eligibility, deriving LOH/LST/TAI scars from allele-specific copy number, deciding between scar-based and mutational-signature HRD methods, or interpreting an HRD result in a BRCA-reverted or low-purity tumor.
The English summary is being prepared. Showing the original description.
Merge PR, wait for deploy, verify production health. 10-step workflow: pre-flight, CI check, readiness gate, merge (respects merge queue), detect platform, wait for deploy, canary verification, revert option, deploy report. Auto-detects Fly, Render, Vercel, Netlify, Heroku, GitHub Actions.
The English summary is being prepared. Showing the original description.
Use when the user wants to roll back GSD commits: the last N, a whole phase, or one plan. Reverts through the phase manifest with dependency checks and a confirmation gate before anything is undone.
The English summary is being prepared. Showing the original description.
Undo a bad change without nuking unrelated work. Use when a specific commit or change broke something.
The English summary is being prepared. Showing the original description.
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
The English summary is being prepared. Showing the original description.
Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
The English summary is being prepared. Showing the original description.
Clean up after (or abandon) a Rails upgrade. Drop NextRails.next? and NextRails.current? branches and retire dual-boot scaffolding (Gemfile.next, Gemfile.next.lock, conditional Gemfile groups), keeping either the next or the current version. Trigger when the user says they are done with the upgrade, want to clean up dual-boot, want to drop NextRails branches, want to finish the upgrade, want to abandon or revert the upgrade attempt, want to roll back to the current Rails version, or want to pause this upgrade hop. Based on FastRuby.io's "Finishing an Upgrade" methodology, extended with an abandon/pause path.
The English summary is being prepared. Showing the original description.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
The English summary is being prepared. Showing the original description.