Update V8 Version

Community

deonmenezes

update-v8-version

Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.

Overview

Publisher	deonmenezes
Repository	`mantishack`
Skill name	`update-v8-version`
Stars	503
Forks	75
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by deonmenezes on GitHub. Read the source before you install it.

Installation

Install the Update V8 Version AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/deonmenezes/mantishack/tree/main/.codex/skills/update-v8-version
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/deonmenezes/mantishack.git /tmp/mantishack
mkdir -p .claude/skills
cp -r /tmp/mantishack/.codex/skills/update-v8-version .claude/skills/update-v8-version

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Update V8 Version in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Update V8 Version on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Update V8 Version is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Update V8 Version

Core Workflow

Read third_party/v8/README.md and follow its version-bump sequence. Treat that document as the release-process source of truth.
Inspect and update the concrete repo surfaces that carry the pin:
- codex-rs/Cargo.toml
- codex-rs/Cargo.lock
- MODULE.bazel
- third_party/v8/BUILD.bazel
- third_party/v8/README.md
- the matching third_party/v8/rusty_v8_<version>.sha256 manifest when the remaining prebuilt inputs change

Keep the existing checksum helpers in the loop:

bash
python3 .github/scripts/rusty_v8_bazel.py update-module-bazel
python3 .github/scripts/rusty_v8_bazel.py check-module-bazel
python3 -m unittest discover -s .github/scripts -p test_rusty_v8_bazel.py

Validate the release-candidate path before broadening the work:
- Prefer checking the v8-canary CI result for the candidate branch or PR when one exists, using GitHub check tooling or gh as appropriate.
- If CI is unavailable or the user asked for a local-only check, run the closest local validation that is practical for the changed surface and say explicitly that it is a local substitute, not the full hosted canary.
If the canary path passes, stop there. Summarize the result and encourage the user to commit the candidate changes or proceed with the release flow they requested. Do not publish tags, releases, or pushes unless the user asked.

Failure Path

Enter this path only when the canary or local build path fails.

Capture the failing target, workflow job, and first actionable error.
Compare the currently pinned version with the target version at the relevant upstream tag or SHA. Inspect both:
- denoland/rusty_v8
- upstream V8 source at the target Bazel-pinned version
Track build-relevant deltas rather than broad source churn:
- generated binding layout changes
- archive or asset naming changes
- GN/Bazel target changes
- custom libc++ / libc++abi / llvm-libc inputs
- sandbox or pointer-compression feature relationships
- patch hunks in patches/ that no longer apply or no longer match upstream
Trace each failing delta back into Codex's build graph:
- MODULE.bazel
- third_party/v8/BUILD.bazel
- .github/scripts/rusty_v8_bazel.py
- .github/workflows/v8-canary.yml
- .github/workflows/rusty-v8-release.yml
Update only the pieces required to restore the target version's build and artifact contract. Keep patch explanations and doc changes close to the affected files.
Re-run the focused validation. If it becomes green, return to the normal workflow and stop with a concise summary plus the remaining release step.

Reporting

Say whether validation came from hosted v8-canary or from a local substitute.
Distinguish "version bump complete" from "release published".
When blocked, report the upstream delta that matters, the Codex file it hits, and the next concrete fix to try.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Update V8 Version AI skill do?

Why use Update V8 Version on TypingMind?

Because you install it once and use it with any model. Update V8 Version is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Update V8 Version in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/deonmenezes/mantishack/tree/main/.codex/skills/update-v8-version. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Update V8 Version?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Update V8 Version?

As many as you like. As long as a model supports skills, you can use Update V8 Version with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Update V8 Version AI skill free?

Yes. It is published on GitHub by deonmenezes under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Openclaw Pr Maintainer

openclaw

OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Update V8 Version

Core Workflow

Failure Path

Reporting

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now