scm

Manage SCM repository versions, builds, and AI-powered build failure diagnostics.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill scm-yuezhen-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scm
Source: https://github.com/yuezhen-huang/my-bytedance-skillhub/tree/main/scm
Command: npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill scm-yuezhen-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing source code repository versions and diagnosing build failures in the SCM platform normally requires navigating web UIs and manually reading build logs. This Skill lets you query repos, create releases, check build status, and get AI-driven failure analysis directly through gdpa-cli commands. ## Core Features & Use Cases - Repository & Version Management: Query repo details, list versions with filters (branch, commit, creator, type), and create new releases from branches or commits. - Build Inspection: Retrieve version status, fetch build logs for specific steps (e.g., unit_test, lint_check), and page through version history. - AI Build Diagnostics: Get root-cause analysis and solutions for failed builds, matching the SCM page's problem analysis view. - Use Case: A release build fails on version 1.0.0.9. Run get_build_troubleshoot to get the AI diagnosis of the error, then get_build_log for the failing step to confirm the fix before creating a new version. ## Quick Start Ask the AI to list the latest versions of the repo tiktok/gdp/gemini_proxy and diagnose why the most recent build failed.

Frequently Asked Questions about scm

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

FAQPage Schema
How do I create a new SCM version from a branch?

Run the create_version action with repo_name and branch_name, optionally setting type (test, online, offline). With the default branch_base strategy, branch_name is required; with commit_base, provide commit_hash instead.

How to get build logs for a specific SCM version?

Use the get_build_log action with version_number plus repo_id or repo_name. You can specify step_name (e.g., unit_test, lint_check); otherwise the step is inferred from the failed or building step.

How do I diagnose a failed SCM build?

Use the get_build_troubleshoot action with version_number and repo identifiers, or pass a record_id directly. It returns AI analysis of error logs, root cause, and solutions matching the SCM page's problem analysis.

What is the difference between repo_id and repo_name in SCM queries?

repo_id is the unique numeric repository ID, while repo_name is the SCM three-part name like ies/gdp/openapi, not the code repository path. Most actions accept either one to identify the repository.

Can I filter the SCM version list by branch or creator?

Yes, get_version_list supports filters including branch, commit_hash, create_user, type, and version, plus pagination via page_num, page_size, limit, and offset.