Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计提醒

configure-workflows配置工作流程

Agent Skill

configure-workflows 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,354

周安装

57

GitHub Stars

28

下载量

474
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:configure-workflows(配置工作流程)
来源仓库:https://github.com/laurigates/claude-plugins
仓库路径:skills/configure-workflows
安装命令:
npx skills add https://github.com/laurigates/claude-plugins --skill configure-workflows
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill configure-workflows

简介

用于检查和配置 GitHub Actions CI/CD 工作流是否符合项目标准。

  • 适合需要标准化构建、测试和发布流程的团队。
  • 可与 release-please 或可重用工作流配合使用,形成完整交付链。
  • 安装前需确认是否包含系统命令执行权限,避免误改关键流水线。
  • configure-workflows 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

/configure:workflows

Check and configure GitHub Actions CI/CD workflows against project standards.

When to Use This Skill

Use this skill when...Use another approach when...
Checking GitHub Actions workflows for compliance with project standardsDebugging a failing CI run (use github-actions-inspection skill)
Setting up container build, test, or release-please workflowsInstalling Claude-powered reusable workflows (use /configure:reusable-workflows)
Updating outdated action versions (checkout, build-push, etc.)Writing a custom workflow from scratch (use ci-workflows skill)
Adding multi-platform builds or GHA caching to existing workflowsConfiguring security-specific workflows (use /configure:security)
Auditing which required workflows are missing from a projectManaging GitHub repository settings or branch protection rules

Context

  • Workflows dir:!find. -maxdepth 1 -type d -name \'.github/workflows\'
  • Workflow files:!find.github/workflows -maxdepth 1 \(-name '*.yml' -o -name '*.yaml' \)
  • Package files:!find. -maxdepth 1 \(-name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)
  • Dockerfile:!find. -maxdepth 1 -name 'Dockerfile*'
  • Release-please config:!find. -maxdepth 1 -name \'release-please-config.json\'

Skills referenced: ci-workflows, github-actions-auth-security

Parameters

Parse from command arguments:

  • --check-only: Report status without offering fixes
  • --fix: Apply fixes automatically

Execution

Execute this GitHub Actions workflow configuration check:

Step 1: Fetch latest action versions

Verify latest versions before reporting outdated actions:

  1. actions/checkout - releases
  2. actions/setup-node - releases
  3. actions/cache - releases
  4. docker/setup-buildx-action - releases
  5. docker/build-push-action - releases
  6. docker/login-action - releases
  7. docker/metadata-action - releases
  8. reproducible-containers/buildkit-cache-dance - releases
  9. google-github-actions/release-please-action - releases

Use WebSearch or WebFetch to verify current versions.

Step 2: Detect project type and list workflows

  1. Check for .github/workflows/ directory
  2. List all workflow files (*.yml, *.yaml)
  3. Categorize workflows by purpose (container build, test, release)

Determine required workflows based on project type:

Project TypeRequired Workflows
Frontendcontainer-build, release-please, renovate (optional: claude-auto-fix)
Pythoncontainer-build, release-please, test, renovate (optional: claude-auto-fix)
Infrastructurerelease-please, renovate (optional: docs, claude-auto-fix)

Step 3: Analyze workflow compliance

Container Build Workflow Checks:

CheckStandardSeverity
checkout actionv4WARN if older
build-push actionv6WARN if older
Multi-platformamd64 + arm64WARN if missing
RegistryGHCR (ghcr.io)INFO
CachingGHA cache enabledWARN if missing
PermissionsExplicitWARN if missing
id-token: writeRequired when provenance/SBOM enabledWARN if missing
Cache scopeExplicit scope= when multiple build jobsWARN if missing
Dead metadata tagsNo type=schedule without schedule triggerINFO
Semver regex escapingDots escaped in type=match patterns (\d+\.\d+)WARN if unescaped
Hardcoded image namesDerive from ${{github.repository}}INFO if hardcoded
Digest outputCapture build-push digest via id: for traceabilityINFO if missing
Job summaryWrite image/digest/tags to $GITHUB_STEP_SUMMARYINFO if missing
Duplicated job conditionsIdentical if: on sibling jobs; suggest gate jobINFO

Release Please Workflow Checks:

CheckStandardSeverity
Action versionv4WARN if older
TokenMY_RELEASE_PLEASE_TOKENWARN if GITHUB_TOKEN
Permissionscontents: write, pull-requests: writeFAIL if missing

Test Workflow Checks:

CheckStandardSeverity
Node version22WARN if older
Lintingnpm run lintWARN if missing
Type checknpm run typecheckWARN if missing
CoverageCoverage uploadINFO

Renovate Workflow Checks:

CheckStandardSeverity
RENOVATE_REPOSITORIES env varMust be set (${{github.repository}})FAIL if missing
checkout actionv6WARN if older
renovatebot/github-actionMinor-pinned (e.g., v46.1.0), not major tagWARN if major-only
Uses reusable workflowPreferred (except infrastructure)INFO if standalone

Claude Auto-Fix Workflow Checks (if present):

CheckStandardSeverity
workflow_run triggerMonitors at least one workflowWARN if misconfigured
Loop preventionSkips fix(auto): commitsFAIL if missing
DeduplicationCaps open auto-fix PRsWARN if missing
Claude Code Actionanthropics/claude-code-action@v1WARN if older
OAuth tokenCLAUDE_CODE_OAUTH_TOKEN secretFAIL if missing
PermissionsMinimal required setWARN if excessive

Step 4: Generate compliance report

Print a formatted compliance report showing workflow status, per-workflow check results, and missing workflows.

If --check-only is set, stop here.

For the report format, see REFERENCE.md.

Step 5: Apply configuration (if --fix or user confirms)

  1. Missing workflows: Create from standard templates
  2. Outdated actions: Update version numbers
  3. Missing multi-platform: Add platforms to build-push
  4. Missing caching: Add GHA cache configuration

For standard templates (container build, test workflow), see REFERENCE.md.

Step 6: Update standards tracking

Update .project-standards.yaml:

components:
  workflows: "2025.1"

Agentic Optimizations

ContextCommand
Quick compliance check/configure:workflows --check-only
Auto-fix all issues/configure:workflows --fix
List workflow filesfind.github/workflows -name '*.yml' -o -name '*.yaml'
Check action versionsrg 'uses:'.github/workflows/ --no-heading
Verify release-please configtest -f release-please-config.json && echo "EXISTS"

Flags

FlagDescription
--check-onlyReport status without offering fixes
--fixApply fixes automatically

See Also

  • /configure:container - Comprehensive container infrastructure (builds, registry, scanning)
  • /configure:dockerfile - Dockerfile configuration and security
  • /configure:release-please - Release automation specifics
  • /configure:all - Run all compliance checks
  • ci-workflows skill - Workflow patterns
  • github-actions-inspection skill - Workflow debugging

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude

32.98%
按下载量换算156

Codex

32.71%
按下载量换算155

Cursor

20.23%
按下载量换算96

Gemini CLI

9.95%
按下载量换算47

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills