Mini-Bili v1.0 技能手册(Skill)

Verify compilation, migration safety, and logging for Mini-Bili Go code changes.

11|2|Updated May 27, 2026
One-click install
npx skills add https://github.com/earthcake2233/cakecake --skill mini-bili-v1-0-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Mini-Bili v1.0 技能手册(Skill)
Source: https://github.com/earthcake2233/cakecake/tree/main
Command: npx skills add https://github.com/earthcake2233/cakecake --skill mini-bili-v1-0-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill manual defines fixed operational procedures to ensure code changes are verifiable, migrations are safe, and logging/ADR practices are followed to maintain high-quality software delivery.

Core Features & Use Cases

  • Compile Validation: Ensure code changes compile successfully before further steps.
  • Database Migrations: Govern and validate incremental schema changes via migration rules.
  • Logging Initialization: Establish structured, leveled logging to replace ad-hoc prints.
  • ADR Documentation: Maintain Architecture Decision Records to capture critical design decisions.
  • Guardrails for Deployment: Enforce safety checks across local development and CI environments.

Quick Start

Execute the Skill to validate a code change by compiling, migrating, and validating logs and ADRs before merging.

Frequently Asked Questions about Mini-Bili v1.0 技能手册(Skill)

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

FAQPage Schema
How do I enforce safe database migrations and compile checks for Go backend changes?

To enforce safe Go backend changes, you verify compilation success, govern incremental database schema migrations, and validate structured logging before merging across local and CI environments.

What is the best way to maintain Architecture Decision Records during CI deployments?

Maintaining Architecture Decision Records (ADRs) during CI involves enforcing hard requirements to capture critical design decisions, ensuring error-code consistency and proper logging practices are documented before staging deployments.

How does structured logging initialization prevent ad-hoc prints in Go CI pipelines?

Structured logging initialization replaces ad-hoc prints by establishing leveled logs validated across local development and CI environments, guaranteeing consistent error tracking and safe deployments.

Do I need specific scripts to validate error-code consistency and ADR updates end-to-end?

Yes, you need scripts to validate end-to-end governance, ensuring compile checks, migration safety, ADR updates, and error-code consistency meet the hard requirements for safe staging deployments.

Can I use this governance process for Go backend migrations outside of staging environments?

This governance process applies across local, CI, and staging environments to guarantee safe deployments, ensuring compilation, safe migrations, and proper logging are verified end-to-end regardless of the environment.

Why does my Go code change fail CI checks if ADR documentation is missing?

Go code changes fail CI checks when ADR documentation is missing because end-to-end governance enforces hard requirements for S-001 through S-014, including mandatory ADR updates and error-code consistency.