whatisgithub

What is codex-speedup-proof?

kappaemme-git/codex-speedup-proof — explained in plain English

Analysis updated 2026-05-18

13PythonAudience · developerComplexity · 2/5LicenseSetup · easy

In one sentence

A Codex skill that finds one safe performance optimization, applies it only with explicit approval, and proves it worked with real before-and-after benchmarks.

Mindmap

mindmap
  root((Speedup Proof))
    What it does
      Finds performance hotspots
      Requires approval gate
      Proves results with benchmarks
    Tech stack
      Python
      Codex skill
      JSON evidence
    Use cases
      Prove optimizations
      Audit performance
      Detect regressions
    Audience
      Developers
      Codex users
    Setup
      npx install
      Restart Codex
      MIT license

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Find and optimize a genuine performance hotspot in a codebase with a proven before-and-after benchmark.

USE CASE 2

Audit a codebase for measurable performance opportunities without changing any code.

USE CASE 3

Investigate why a branch became slower compared to main using the same benchmark workload.

What is it built with?

PythonCodexMarkdownJSON

How does it compare?

kappaemme-git/codex-speedup-proof1lystore/awaek47cid/wp2shell-lab
Stars131313
LanguagePythonPythonPython
Setup difficultyeasymoderatemoderate
Complexity2/52/54/5
Audiencedevelopervibe coderresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an existing Codex installation to use the skill.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

Codex Speedup Proof is a skill add-on for OpenAI's Codex coding assistant that tries to make performance optimization claims trustworthy instead of taking them on faith. Rather than looking at code and declaring it faster because the structure looks better, the skill finds a likely performance hotspot, proposes exactly one focused change to fix it, and then measures the same realistic workload both before and after the change to see whether it actually helped. The result is always one of three honest verdicts: proven, inconclusive, or regression, never a made up percentage improvement. Before touching any files, the skill has to show the user a full proposal: which files it plans to change, the exact transformation it intends to make, what behavior needs to stay identical, the benchmark and test plan, and the main risk involved. It then stops and waits for explicit approval, and that approval only covers the one proposal shown, so a different optimization needs a fresh approval. Once approved, it applies the single change, preserving things like outputs, ordering, error behavior, APIs, and permissions, then runs the project's existing tests, typechecks, and build process. It rejects changes that turn out to be noisy in their measurements, actually slower, or that break existing behavior. A result only counts as proven when correctness checks pass, the same representative workload is used before and after, the measurements are stable, and the improvement clearly exceeds normal benchmarking noise. The skill also supports an audit mode that ranks performance opportunities without changing any code, and a regression mode for comparing a branch against main to find out what got slower. Installation is a single command using npx, which places the skill into a Codex skills folder, or it can be installed manually by cloning the repository and copying the folder in directly. After installing, Codex needs to be restarted. Output is written as a Markdown report that renders on GitHub plus a machine readable JSON evidence file, so the result can be reproduced. The project is released under the MIT license.

Copy-paste prompts

Prompt 1
Use $speedup-proof to find the slowest safe hotspot in this codebase and propose one optimization with a benchmark plan.
Prompt 2
Use $speedup-proof in audit mode to rank performance opportunities without modifying any files.
Prompt 3
Use $speedup-proof in regression mode to compare my current branch against main and find what got slower.
Prompt 4
Explain what evidence codex-speedup-proof requires before it will call a result PROVEN.

Frequently asked questions

What is codex-speedup-proof?

A Codex skill that finds one safe performance optimization, applies it only with explicit approval, and proves it worked with real before-and-after benchmarks.

What language is codex-speedup-proof written in?

Mainly Python. The stack also includes Python, Codex, Markdown.

What license does codex-speedup-proof use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is codex-speedup-proof to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is codex-speedup-proof for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.