'revert' 검색 결과

Improve code through repeated experiments against a measurable target, such as execution time or memory use. After defining scope and constraints, the agent tests changes, keeps improvements, reverts unsuccessful attempts, and logs results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reduce execution time through measured code experiments
• Optimize memory use or bundle size
• Compare changes using benchmark results

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether cloud detection rules trigger
• Testing log ingestion and alert routing
• Running joint attack and defense exercises

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare checks for an upcoming production release
• Review a release with database migrations
• Verify feature flags and CI status before deployment

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix missing fields and instructions in a skill
• Address findings from category checks
• Compare check results before and after edits

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Registering a feature before implementation
• Releasing a feature to selected organizations
• Separating cloud and self-hosted availability

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restore a previous release after a production incident
• Check database compatibility before a rollback
• Prevent frontend rebuilds from overwriting a rollback

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Apply selected patches after a meta-optimize run
• Review staged changes immediately before applying them
• Keep backups for reverting skill changes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding GSAP animations to React components
• Restricting animations to elements within one component
• Cleaning up animations when components unmount

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a custom bench or object to CARLA
• Fix imported props missing from the blueprint library
• Import a folder of props organized by tag

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare checks for an upcoming production release
• Review a release with database migrations
• Verify feature flags and CI status before deployment

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate the reasoning behind a built-in type
• Assess a proposed type override in ts-reset
• Find rejected or reverted 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding code patterns to prioritize for cleanup
• Preparing measurement files for an improvement loop
• Repeating targeted edits to reduce casts to any

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write commit messages using Conventional Commits
• Organize branches and Pull Request reviews
• Resolve conflicts during 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write commit messages using Conventional Commits
• Organize branches and Pull Request reviews
• Resolve conflicts during 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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Listing available project checkpoints
• Restoring files after an unsuccessful change
• Previewing files affected by a rollback

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Git-aware undo by logical work unit (track, phase, or task)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Undo a bad change without nuking unrelated work. Use when a specific commit or change broke something.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.