Workflow Skill — 工作流程相關修改指南

Standardize CI and workflow modifications with checklists and commit templates.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/jvtutorcorner-sketch/jvtutorcorner-rwd --skill workflow-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Workflow Skill — 工作流程相關修改指南
Source: https://github.com/jvtutorcorner-sketch/jvtutorcorner-rwd/tree/main/.agents/skills/workflow
Command: npx skills add https://github.com/jvtutorcorner-sketch/jvtutorcorner-rwd --skill workflow-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the process for documenting and implementing changes related to CI/workflow, ensuring consistency in modifications to GitHub Actions, CI scripts, and build/cache configurations.

Core Features & Use Cases

  • Standardized Checklists: Provides a checklist for verifying workflow changes across different runners, managing secrets, and validating caching.
  • Commit Message Conventions: Recommends using Conventional Commits for clear and structured commit messages related to workflows.
  • PR Description Template: Offers a template for Pull Request descriptions, ensuring all necessary information is included for review.
  • Use Case: When updating a GitHub Actions workflow to include a new deployment stage, use this Skill's checklist to ensure all necessary permissions and configurations are in place and follow the recommended commit message format.

Quick Start

Use the workflow skill to add a new build-cache job to the CI workflow.

Frequently Asked Questions about Workflow Skill — 工作流程相關修改指南

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

FAQPage Schema
How do I standardize commit messages for GitHub Actions and CI workflow changes?

To standardize commit messages for GitHub Actions and CI workflow changes, apply Conventional Commits templates. This ensures structured, clear commit histories specifically for modifications to CI scripts, build configurations, and cache settings.

What should I include in a PR description when updating CI scripts and build configurations?

A PR description for CI script and build configuration updates should include a standardized template covering necessary permissions, runner verification, and cache validation details. This ensures all critical information is present for reliable review.

How do I use a checklist to verify GitHub Actions workflow changes across different runners?

Use a standardized workflow checklist to verify GitHub Actions changes across different runners. This checklist guides you through managing secrets, validating caching, and checking build configurations to ensure reliable workflow management.

When do I need to follow a standardized workflow modification process for GitHub Actions?

You need to follow a standardized workflow modification process for GitHub Actions whenever updating deployment stages, modifying CI scripts, or changing cache settings. This ensures consistency and prevents configuration errors during automation updates.

Does this approach work for adding a new build-cache job to an existing CI workflow?

Yes, this approach works for adding a new build-cache job to a CI workflow. It provides a standardized checklist to ensure all necessary permissions and configurations are in place, followed by a recommended commit message format.

What is the best way to manage secrets and validate caching when updating GitHub Actions workflows?

The best way to manage secrets and validate caching when updating GitHub Actions workflows is by using a standardized checklist. This verifies that all runner configurations and cache settings are correctly implemented before committing changes.