Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

mlx-fix-test-cpp

Estrelas38

Forks4

Atualizado12 de julho de 2026 às 18:58

Build MLX, reproduce one failing C++ test, and implement the smallest Vulkan-only fix. Use when asked to repair a C++ test failure in this repository while preserving test code and avoiding unrelated fixes.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

goniz

goniz/mlx-vulkan

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	mlx-fix-test-cpp
description	Build MLX, reproduce one failing C++ test, and implement the smallest Vulkan-only fix. Use when asked to repair a C++ test failure in this repository while preserving test code and avoiding unrelated fixes.

Fix One Vulkan C++ Test

Fix exactly one C++ failure per invocation.

Run ./dev.sh build.
After the build completes, run ./dev.sh test-cpp --fail-after=1.
Identify the first failing test and reproduce only that failure as needed.
Do not modify test code. Modify implementation only under mlx/mlx/backend/vulkan/.
Before editing, inspect corresponding CUDA and Metal implementations under mlx/mlx/backend/cuda/ and mlx/mlx/backend/metal/.
Make the smallest correct fix consistent with existing backend patterns and the async Vulkan pipeline policy.
Run ./dev.sh build, then ./dev.sh test-cpp --fail-after=1 sequentially to verify the addressed failure. Continue only on the same failure until it passes or a clear blocker remains.
After implementation changes, run ./dev.sh generate to validate inference output coherence.

Report the failure addressed, Vulkan files changed, reference backend files consulted, and final test and generation results. Do not fix later or unrelated failures.

Mais deste repositório

mesmo repositório

mlx-benchmark

goniz/mlx-vulkan

Run and compare MLX Vulkan inference benchmarks. Use when asked to benchmark this repository, measure a change, run bf16 or 8-bit MLX performance tests, or compare current results with the README baseline.

2026-07-1638

mlx-vulkan-review-fix

goniz/mlx-vulkan

Review the MLX Vulkan backend for one major async-pipeline or inference-performance issue, obtain user approval, implement the scoped fix, then run full MLX validation, benchmarks, and model generation reporting. Use when the user wants an end-to-end Vulkan improvement workflow with an explicit review-before-fix approval boundary.

2026-07-1338

mlx-commit

goniz/mlx-vulkan

Commit changes solely within the MLX submodule in this Vulkan repository. Use when asked to inspect, stage, and commit work in `mlx/` without modifying or committing the `mlx-vulkan` parent repository.

2026-07-1238

mlx-create-pr

goniz/mlx-vulkan

Commit MLX submodule changes, run required Vulkan benchmarks, push a branch, and open a PR against `goniz/mlx`. Use when asked to create a pull request for MLX Vulkan work, especially when an issue number must be closed and bf16 plus 8-bit benchmark results are required.

2026-07-1238

mlx-fix-test-py

goniz/mlx-vulkan

Build MLX, reproduce one failing Python test, and implement the smallest Vulkan-only fix. Use when asked to repair a Python test failure in this repository while preserving test code and avoiding unrelated fixes.

2026-07-1238

mlx-issue

goniz/mlx-vulkan

Investigate and address a `goniz/mlx-vulkan` GitHub issue in the MLX submodule. Use when given an issue number and asked to read the issue, plan the work, reproduce a reported bug, implement the scoped fix, and work from an MLX feature branch based on `goniz/mlx:feat/vulkan`.

2026-07-1238

name	mlx-fix-test-cpp
description	Build MLX, reproduce one failing C++ test, and implement the smallest Vulkan-only fix. Use when asked to repair a C++ test failure in this repository while preserving test code and avoiding unrelated fixes.

Fix One Vulkan C++ Test

Fix exactly one C++ failure per invocation.

Run ./dev.sh build.
After the build completes, run ./dev.sh test-cpp --fail-after=1.
Identify the first failing test and reproduce only that failure as needed.
Do not modify test code. Modify implementation only under mlx/mlx/backend/vulkan/.
Before editing, inspect corresponding CUDA and Metal implementations under mlx/mlx/backend/cuda/ and mlx/mlx/backend/metal/.
Make the smallest correct fix consistent with existing backend patterns and the async Vulkan pipeline policy.
Run ./dev.sh build, then ./dev.sh test-cpp --fail-after=1 sequentially to verify the addressed failure. Continue only on the same failure until it passes or a clear blocker remains.
After implementation changes, run ./dev.sh generate to validate inference output coherence.

Report the failure addressed, Vulkan files changed, reference backend files consulted, and final test and generation results. Do not fix later or unrelated failures.