007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Creates, debugs, and optimizes GitHub Actions workflow YAML files. Recommends current action versions with SHA pinning from a daily-updated index of 120+ actions. Configures matrix builds, dependency caching, reusable workflows, OIDC authentication, secrets management, and runner selection. Reviews existing workflows for outdated actions, security issues, and performance problems. Use when the user asks about GitHub Actions, workflows, CI/CD, .github/workflows, any action by name (actions/checkout, setup-node, setup-python, etc.), or workflow optimization.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Comprehensive knowledge for creating, reviewing, and optimizing GitHub Actions workflows with current action versions and best practices.
!command -v actionlint 2>/dev/null && echo "actionlint: installed" || echo "actionlint: not installed"
!command -v act 2>/dev/null && echo "act: installed" || echo "act: not installed"
If either tool is missing, suggest the user install them:
brew install actionlint — workflow linter that catches syntax errors, type mismatches, and expression problems offlinebrew install act — runs workflows locally in Docker without pushingConsult actions-index.json in this skill directory for current versions of 120+ popular actions. The index is updated daily and organized by category.
Always verify versions before recommending — use the index or fetch from GitHub releases if needed.
| Pattern | When to Use | Reference |
|---|---|---|
| Matrix builds | Test across versions/platforms | references/patterns-matrix-builds.md |
| Caching | Speed up dependency installation | references/patterns-caching.md |
| Artifacts | Share files between jobs | references/patterns-artifacts.md |
| Reusable workflows | Share workflows across repos | references/patterns-reusable-workflows.md |
| Concurrency | Prevent duplicate runs | references/patterns-concurrency.md |
| Environments | Deployment gates/approvals | references/patterns-environments.md |
| Composite actions | Create custom actions | references/patterns-composite-actions.md |
| Topic | Key Points | Reference |
|---|---|---|
| Secrets | Never hardcode, use OIDC when possible | references/security-secrets.md |
| Permissions | Principle of least privilege | references/security-hardening.md |
| Supply chain | Pin actions, review dependencies | references/security-supply-chain.md |
Every workflow should include these often-missed fields:
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 30
Full JSON Schema for workflow validation: references/github-action.schema.json
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
For custom caching, see references/patterns-caching.md.
strategy:
fail-fast: false
matrix:
os: [ubuntu-latest, macos-latest, windows-latest]
node: [18, 20, 22]
exclude:
- os: windows-latest
node: 18
include:
- os: ubuntu-latest
node: 20
coverage: true
jobs:
build:
runs-on: ubuntu-latest
steps: [...]
test:
needs: build
runs-on: ubuntu-latest
steps: [...]
deploy:
needs: [build, test]
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps: [...]
For conditional execution patterns (if:, always(), failure()), trigger event configuration, and expression syntax, see references/triggers.md and references/expressions.md.
permissions:
contents: read
jobs:
build:
permissions:
contents: read
deploy:
permissions:
contents: read
id-token: write
packages: write
# Good: Pin to full SHA
- uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
# Acceptable: Pin to major version
- uses: actions/checkout@v6
# Bad: Unpinned or floating
- uses: actions/checkout@main
- uses: actions/checkout
Prefer OIDC over long-lived credentials. See references/security-secrets.md for setup guides for AWS, GCP, and Azure.
When reviewing workflows, generate an ASCII flowchart showing job dependencies.
Before pushing workflow changes, verify correctness:
Lint with actionlint — catches syntax errors, type mismatches, and expression problems that YAML parsers miss:
actionlint .github/workflows/*.yml
Test locally with act — runs workflows in Docker without pushing:
act push --job build
act pull_request -e event.json
Check workflow run logs — after pushing, verify in the Actions tab:
cache hit: true)Validate secrets access — workflows fail silently when secrets are missing. Verify required secrets exist in repo/org settings before relying on them.
When reviewing workflows, check:
actions-index.json)timeout-minutes set to prevent runaway jobsfail-fast: false if matrix jobs are independentpermissions declaredadd-mask for dynamic secrets)concurrency configured to prevent duplicate runsif:) used appropriatelycontinue-on-error only where truly neededAll reference files are in references/:
| File | Topic |
|---|---|
workflow-syntax.md | Complete workflow YAML reference |
expressions.md | Expression syntax, contexts, functions |
triggers.md | All event triggers with examples |
runners.md | Runner selection, self-hosted setup |
permissions.md | GITHUB_TOKEN scopes, OIDC setup |
troubleshooting.md | Common errors and solutions |
patterns-matrix-builds.md | Matrix strategies, include/exclude |
patterns-caching.md | Cache action, custom keys, restore strategies |
patterns-artifacts.md | Upload/download, retention, cross-job sharing |
patterns-reusable-workflows.md | workflow_call, inputs, secrets |
patterns-concurrency.md | Groups, cancel-in-progress |
patterns-environments.md | Deployment environments, protection rules |
patterns-composite-actions.md | Creating custom actions |
security-secrets.md | Management, rotation, OIDC setup |
security-hardening.md | Permissions, pinning, CodeQL |
security-supply-chain.md | Dependency review, Dependabot |
Working templates in examples/: ci-node.yaml, ci-rust.yaml, deploy-aws.yaml, release-please.yaml
actions-index.json — Current versions of 120+ popular actions (updated daily)tracked-actions.yaml — List of tracked actions by categoryまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。