gitcode-space-iter

Automate GitCode Space rebuild validation via web UI and smoke sentinels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork and manual browser checking involved in verifying that a freshly pushed GitCode Space deployment rebuilds and produces the expected startup outcome.

Core Features & Use Cases

  • Deterministic rebuild loop: Resets the Space, reloads the app page to avoid cached iframes, and waits for explicit startup smoke sentinels.
  • Result capture across UI boundaries: Reads structured output from the Gradio iframe via Chrome DevTools Protocol snapshots, and falls back to log-panel text when the iframe disappears on failure.
  • Resource hygiene: Pauses the Space after the run completes to free limited compute on the free tier.
  • Typical use case: After pushing a change to a Space’s main-backed deployment branch, automatically confirm the container reached smoke OK or surface smoke FAILED details without a manual reload-and-check cycle.

Quick Start

Use gitcode-space-iter to push your change, trigger the Space reset, wait for the smoke output, capture the Gradio result, and then pause the Space so compute is released.

Frequently Asked Questions about gitcode-space-iter

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

FAQPage Schema
How do I automate smoke testing for a GitCode Space deployment?

Automating smoke testing for a GitCode Space deployment involves driving the web UI to reset, rebuild, and confirm startup using stable visible-button selectors. The Skill waits for explicit smoke sentinels like smoke OK to verify the Gradio app started successfully.

How does UI automation capture Gradio iframe output during a Space rebuild?

UI automation captures Gradio iframe output during a Space rebuild by reading structured results via Chrome DevTools Protocol snapshots. If the iframe disappears on failure, it falls back to reading the container log text from the log panel to surface failure details.

Do I need chrome-devtools MCP to run GitCode Space validation?

Yes, you need chrome-devtools MCP availability to run GitCode Space validation. The Skill requires the chrome-devtools MCP to drive the web UI, trigger lifecycle actions, and read iframe snapshots or container logs to confirm the deployment outcome.

What is the best way to verify a Gradio app startup on GitCode without manual browser checking?

The best way to verify a Gradio app startup on GitCode without manual browser checking is using an automated validation iteration. It resets the Space, reloads the app page to avoid cached iframes, and waits for explicit startup smoke sentinels to confirm the result.

Why does my GitCode Space compute keep running after a deployment smoke test?

Your GitCode Space compute keeps running after a deployment smoke test if it is not paused post-run. This Skill applies resource hygiene by automatically stopping the Space compute after the validation loop completes to free limited free-tier resources.

Can I use this automated rebuild loop if the GitCode Space pages are not open?

No, you cannot use this automated rebuild loop if the specific GitCode pages are not open. The Skill requires two specific GitCode pages to be open in the browser to trigger lifecycle actions and read the Gradio iframe output successfully.