gitcode-webide

Retrieve byte-exact WebIDE terminal outputs via git transit from NPU hosts.

7|4|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ultism/svdquant-kernels --skill gitcode-webide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcode-webide
Source: https://github.com/ultism/svdquant-kernels/tree/main/.claude/skills/gitcode-webide
Command: npx skills add https://github.com/ultism/svdquant-kernels --skill gitcode-webide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of reliably retrieving exact kernel/build/log output from Huawei CodeArts WebIDE when terminal text is rendered on a canvas and cannot be scraped or OCR’d accurately.

Core Features & Use Cases

  • Byte-level exact output capture: Redirects terminal output into tracked files and reads results back locally via git show for fidelity.
  • End-to-end transit workflow: Runs commands on the 910B3 NPU host, commits on a scratch branch, pushes to gitcode, then fetches and displays the artifacts locally.
  • Browser-state aware execution: Uses chrome-devtools MCP page selection to target the correct WebIDE tab and ensures the xterm terminal input focus before running commands.

Quick Start

Tell your AI assistant to drive the open CodeArts WebIDE terminal on the 910B3 instance, run your build or NPU command with output redirected to tmp/<topic>/out.log, push a scratch/<topic> branch to gitcode, and then retrieve the exact logs locally using git show.

Frequently Asked Questions about gitcode-webide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract exact build logs from a WebIDE terminal when the output is rendered on a canvas?

To retrieve exact terminal output from a CodeArts WebIDE, redirect commands to tracked files, push a scratch branch to gitcode, and read the logs locally using git show for byte-level fidelity without OCR.

Can I capture 910B3 NPU build logs locally without using OCR on the terminal screen?

Yes, you can capture NPU build logs without OCR by redirecting terminal output to tracked files, using git as a transit layer to push a scratch branch, and fetching exact artifacts locally via git show.

What is the best way to retrieve non-scrapable xterm output from a CodeArts WebIDE session?

The best way to retrieve non-scrapable xterm output is using git as a transit layer: redirect output to tracked files, commit to a scratch branch, push to gitcode, and pull exact logs locally.

Does the WebIDE terminal automation workflow require specific browser state setup?

Yes, WebIDE terminal automation requires chrome-devtools MCP access to target the correct browser tab and ensure the xterm terminal has input focus before running commands and capturing output.

Why does scraping WebIDE terminal text fail and how does git transit solve it?

Scraping WebIDE terminal text fails because output is canvas-rendered. Git transit solves this by redirecting output to tracked files and reading them back locally with byte-level fidelity.

What are the limitations of using git to pull WebIDE build artifacts from a 910B3 NPU host?

Limitations include requiring chrome-devtools MCP access for tab selection, needing terminal focus before running commands, and depending on network connectivity to push scratch branches to gitcode for local readback.