Results for “fix”

Stripe CLI の `stripe fixtures` コマンドで実行可能な fixture JSON を、対話的に整理しながら生成・検証する。test_clock を使った時間進行、サブスクのライフサイクル、失敗カードでの payment_intent 失敗、Connect 配下の Destination charge、bulk 件数のテスト顧客作成など、複数ステップの API リクエスト連鎖を扱う。「Stripe の fixture を書いて」「fixtures.json を作って」「このシナリオを fixture 化」「テストデータを大量に作りたい」「サブスクの月次失敗をテストしたい」「stripe trigger と fixture どっち使う」のような依頼で起動する。"fixture" という単語が無くても、複数ステップの Stripe テストデータ準備、 test clock を使った時間進行、 bulk なテスト顧客作成、 失敗パターンの再現といった意図が見えたら起動する。単発 API 呼び出しが目的なら起動せずに `stripe trigger` か API 1コールを案内する。

The English summary is being prepared. Showing the original description.

copy_tuner（CopyTuner / copy_tuner_client）で集中管理している i18n データを、prefix（正規表現）単位で Rails 標準の config/locales（YAML）管理へ移すスキル。gem の local_first_key_regexp を使うので、 gem を残したまま特定 prefix だけをローカル管理にできる（部分ローカル化）。1 回の実行で 1 prefix。 全 prefix を移して gem ごと撤去したい場合は繰り返し、完了後 copy-tuner-to-locales-cleanup スキルへ進む。 対象 prefix はスキル引数で指定でき、未指定なら export を俯瞰して選定する。

The English summary is being prepared. Showing the original description.

pr-auto-fix プラグインの監視ループを起動するトリガースキル。Hook で PR 作成が検知された後、Claude が `pr-auto-fix:auto-fix-pr` として呼び出すと Monitor (`pr-auto-fix-watcher`) がバックグラウンドで起動する。Monitor からの通知を受けて pr-auto-fixer エージェントへディスパッチする責務を持つ。ユーザーが手動で起動するスキルではなく、Hook 経由でのみ呼ばれる前提。

The English summary is being prepared. Showing the original description.

Write and debug Python regressions with PyFixest using a reference for model formulas, estimation functions, and standard errors. It also covers extracting results, comparing models, and producing regression tables and plots, including models that account for group differences.

• Write fixed-effects regression code
• Check clustered standard error settings
• Compare models in tables and plots

Drive repeated debugging cycles with the required diagnose skill: establish evidence for a cause, choose one focused fix, and rerun the original validation. Reassess after each change until no credible fix remains or further progress requires user input.

• Repeating bug fixes and verification until validation is clean
• Checking performance changes against original measurements
• Investigating regressions after each fix

Audit whether an AI agent follows its intended purpose, business rules, and permission boundaries. The skill guides setup discovery, test configuration, execution against an agent endpoint or substitute model, and interpretation of scores from selected judging models.

• Auditing an agent's compliance with business rules
• Testing permission boundaries and dangerous tools
• Evaluating an agent through its HTTP endpoint

Handle critical bugs in a released game through an emergency workflow. Investigate the cause, prepare a minimal fix, track reviews and tests, and verify the fix reaches development branches, with deployment approval and post-release checks recorded.

• Responding to crashes or data loss in a released game
• Preparing a minimal emergency patch
• Tracking patch approvals, tests, and rollback plans

Scan interface code for missing, uneven, or awkward animations and receive a motion score with findings. Choose a fix service to adjust animation values or install component recipes, then scan again to check the changes.

• Review animation quality after interface changes
• Standardize timing and hover transitions
• Apply motion recipes to recognized components

Organize Playwright tests with guidance on Page Object Model, a pattern that groups code by page. Learn how to structure page objects and decide when fixtures or helpers offer a simpler approach.

• Organizing Playwright test code
• Choosing whether to introduce page objects
• Comparing POM, fixtures, and helpers

review-all を実行し、指摘内容をコードに反映、bun run c / bun run lint / bun test で自己検証し、CONVERGED/NOT_CONVERGED の収束判定付き完了レポートを /tmp/arima-review-fix-result.md に出力する。レビュー→修正→検証→レポートを一気通貫で行うスキル。スコープ引数は /review-all と同じ（wt / PR #N / vs:<branch> / range / ファイル列挙）。review-fix-loop からの自動呼び出し（mode=non-interactive）にも対応。Use when user says 'レビューして直して', 'review and fix', '自動修正', 'レビュー反映', or when invoked by review-fix-loop.

The English summary is being prepared. Showing the original description.

Using AutoFixture to automatically generate test data basic skill. Used when quickly generating test objects, reducing boilerplate code, and implementing anonymous testing. Covers Fixture.Create, CreateMany, circular reference handling, and xUnit integration. Keywords: autofixture, fixture, auto-generate test data, test data generation, anonymous testing, anonymous testing, fixture.Create, CreateMany, fixture.Build, Create<T>, AutoFixture.Xunit2, OmitOnRecursionBehavior, IFixture, generate test data, generate test data

The English summary is being prepared. Showing the original description.

Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.

• Fix linting errors in a pull request
• Resolve TypeScript errors in a pull request
• Apply fixes to a pull request from a fork

Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.

• Fixing vulnerabilities reported by Strix
• Prioritizing remediation by severity
• Retesting original exploits after code changes

Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.

• Implement and verify a reproducible bug fix
• Submit an upstream Codex pull request
• Deliver a tested LazyCodex patch in an issue

Fix bugs reported in GitHub issues through a reproduce-first process. The workflow guides code changes, build checks, verification, regression tests that check for recurring failures, and review before considering the fix complete.

• Fixing a bug reported in a GitHub issue
• Reproducing a user-reported problem before editing code
• Verifying a fix and adding regression tests

Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.

• Fixing audit findings with test verification
• Prioritizing findings by severity
• Limiting how many findings are fixed

Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.

• Implement and verify a reproducible bug fix
• Submit an upstream Codex pull request
• Deliver a tested LazyCodex patch in an issue

Fix a specific bug or problem in a {{engine_name}} project. Supports two modes — immediate fix or plan-first. Without arguments executes existing .unikit/code/FIX_PLAN.md. Checks {{engine_name}} compilation, suggests test coverage, and creates self-improvement patches. Use when user says "fix bug", "debug this", "something is broken", "fix the tests", "fix the errors in the tests", "read the errors in the {{engine_name}} console logs and fix the problems", or pastes an error message or {{engine_name}} console log. Also trigger when user shares a NullReferenceException, MissingReferenceException, compilation error, or any {{engine_name}}-specific error.

The English summary is being prepared. Showing the original description.

Diagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).

The English summary is being prepared. Showing the original description.

Complete guide for AutoFixture advanced customization techniques. Use when you need to customize AutoFixture builders or handle special type test data generation rules. Covers DataAnnotations automatic integration, ISpecimenBuilder implementation, priority management. Includes DateTime/numeric range builders, generic design, and fluent extension methods. Keywords: autofixture customization, autofixture customize, autofixture customization, specimen builder, ISpecimenBuilder, RandomDateTimeSequenceGenerator, NumericRangeBuilder, DataAnnotations autofixture, fixture.Customizations, Insert(0), custom builder, NoSpecimen, generic builder

The English summary is being prepared. Showing the original description.

Coordinate bug fixes by assigning each phase to an appropriate ECC agent. First reproduce the problem with a failing test, then fix it, review the changes, and request approval before committing.

• Fixing crashes or incorrect output
• Adding a test to catch a recurring bug
• Investigating a bug with an unclear cause

Track documented code fixes across releases with a signed manifest, a list of fixes and their identifying text. Verify that markers remain in source files, inspect file changes, and use recorded history to identify commits associated with regressions.

• Check that documented fixes remain before a release
• Trace a regression through release history
• Verify signed fix records in CI

Read design review notes attached to a pull request’s screenshots, locate the affected components, and fix the product code using the team’s design rules. Repeat the review and inspect screenshots to verify the result.

• Resolving design notes on a pull request
• Reproducing reported layout problems locally
• Fixing shared components behind repeated UI issues

Review code changes on GitHub or GitLab and investigate failed CI checks, the automated checks run on code. Use logs to guide fixes, push commits, and share review comments and repair summaries.

• Review code changes and leave inline comments
• Investigate failed CI checks and fix the code
• Share fix summaries with human reviewers