skills.rest
yuezhen-huang
yuezhen-huangCOMMUNITY
Explore all skills by this author →
GitHub

bits-dev-workflow

Orchestrates BITS DevOps development workflows from task creation through deployment, testing, and stage approval.

Updated Apr 30, 2026
Search Tags:#workflow#devops#code review#deployment#pipeline#session recovery#bits
One-click install
npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill bits-dev-workflow-yuezhen-huang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bits-dev-workflow
Source: https://github.com/yuezhen-huang/my-bytedance-skillhub/tree/main/bits-dev-workflow
Command: npx skills add https://github.com/yuezhen-huang/my-bytedance-skillhub --skill bits-dev-workflow-yuezhen-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Driving a BITS DevOps development cycle involves many manual steps—creating dev tasks, pushing code, running pipelines, testing interfaces, and passing development and access stages. This Skill automates and coordinates that entire flow with a resumable, status.json-driven state machine so nothing is lost between sessions. ## Core Features & Use Cases - End-to-End Phase Orchestration: Guides eight phases (info collection, task setup, deploy, testing, dev stage pass, code review, access stage pass, completion) with mandatory user confirmation checkpoints. - Session Recovery: Maintains .gdpa/{session-id}/status.json so an interrupted workflow can be resumed exactly where it left off by reusing the same session_id. - Automated Parameter Detection: Auto-detects PSM from repo files, fetches BITS templates and recent Meego stories, and derives test environment (VRegion/VDC/lane) from lane info. - Use Case: A developer says "create a BITS dev task for my feature branch and run the deployment plus testing cycle"—the Skill collects and confirms parameters, creates or reuses the BITS task, pushes code, monitors pipelines, runs bam-query interface tests and argos-query log checks, then drives stage approvals through to a final summary report. ## Quick Start Ask the assistant to start a BITS DevOps workflow for your current branch, for example: create a BITS dev task for this repo, deploy it, run interface tests, and drive it through the development and access stages.

Frequently Asked Questions about bits-dev-workflow

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

FAQPage Schema
How do I create a BITS dev task and run the deployment pipeline?▼

Start the workflow and it auto-detects your PSM, reads or prompts for the BITS space_id, confirms parameters, then calls create_dev_task and triggers the self-test pipeline via run_pipeline. All parameters are shown in a confirmation sheet before anything is executed.

How do I resume an interrupted BITS workflow session?▼

Provide your previous session_id and the workflow reads .gdpa/{session-id}/status.json to locate current_phase. Phases marked in_progress continue from the last history entry, completed phases are skipped, and failed phases are analyzed for retry.

What is the difference between bits-dev-workflow and base-workflow?▼

bits-dev-workflow is for BITS DevOps based development flows with BITS tasks, lanes, and stage approvals. For DevFlow based workflows, use base-workflow instead, as stated in the skill description.

How does the workflow handle a failed BITS pipeline?▼

It calls get_pipeline_run to inspect each Job's status and fail_reason, and follows driven_pipeline_run_id into child pipelines when needed. The failure details and fix suggestions are shown to the user, who decides whether to fix code and redeploy.

Can I reuse an existing BITS dev task instead of creating a new one?▼

Yes. The workflow matches open dev tasks by branch, accepts a user-provided BITS link or dev_task_id, and validates the task is OPEN. If the task's branch differs from your local branch, it presents three resolution options before proceeding.

Why must the same session_id be reused across gdpa-cli run commands?▼

The workflow state, phase artifacts, and recovery chain all live under .gdpa/{session-id}/. Changing or omitting the session_id breaks status.json continuity, so the skill mandates explicitly passing --session-id on every gdpa-cli run call.

Related Skills

Explore More Software Engineering Skills→
withmartian-sandbox-darksidewithmartian-sandbox-darkside

using-git-worktrees

Create isolated git worktrees for parallel feature development without branch switching.

Official
Intermediate
umputunumputun
439

new

Automate release creation and publishing across GitHub, GitLab, and Gitea.

Community
Advanced
CODE-SAURABHCODE-SAURABH
2

sre-canary

Verify production deployments and canary releases for health and performance regressions.

Community
Advanced
eatbreadseatbreads
1

bits-devops

Automate Bits dev tasks, release tickets, and train bindings via CLI.

Community
Advanced