007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a complete .github/workflows/ set for a new project: CI (build/test/lint), CD (workflow_dispatch with env choice + OIDC + ECR), security-scan (gitleaks + dependency scan + CodeQL), and optional database-migration. Use this skill when the user wants to add GitHub Actions CI/CD to a project that does not already have it, or when they want to add missing workflows alongside existing ones.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
For Claude Code AI Assistant
This skill generates a production-ready .github/workflows/ set for a project, replicating the patterns used in zoe and xenia/pms. It auto-detects the project stack and produces correctly-wired workflow files with all required secrets and variables documented inline.
| File | Purpose |
|---|---|
.github/workflows/ci.yml | Runs on PR open/sync: build, test, lint. Stack-aware. |
.github/workflows/cd.yml | Manual deploy via workflow_dispatch with environment choice (staging / prod). OIDC auth, ECR image build/push, ECS deploy. |
.github/workflows/security-scan.yml | GitLeaks secret scan + OWASP dependency check + CodeQL SAST. Scheduled daily + PR trigger. |
.github/workflows/database-migration.yml | Optional. Flyway migrations via Gradle. Validates on PR, deploys on workflow_dispatch. |
.gitleaks.toml | GitLeaks configuration (dropped at project root alongside .github/). |
The script scans the project root for these marker files:
| Marker | Detected stack |
|---|---|
gradlew or pom.xml | JVM/Gradle (default) |
package.json | Node.js |
Cargo.toml | Rust |
go.mod | Go |
If none is found, JVM/Gradle is used (the user's primary stack).
cd.yml uses workflow_dispatch with an environment input — no auto-deploy on push to main. This is intentional and must not be changed.cd.yml header as arn:aws:iam::<account>:role/<project>-gha-deploy-<env>.deploy-${{ inputs.environment }} with cancel-in-progress: false. Prevents two prod deploys racing. This is the xenia/pms pattern.--force required to overwrite. Existing files are never silently clobbered. New files are always added side-by-side.| User phrasing | Action |
|---|---|
| "add CI/CD to my project", "scaffold GitHub Actions", "set up workflows" | Run init in the project directory |
| "add CI/CD without the database migration" | Run init --no-db-migration |
| "preview what would be created" | Run init --dry-run |
| "overwrite my existing workflows" | Run init --force |
| "add security scanning" | Run init — security-scan.yml is always included |
If the user is working in a specific project directory, use that directory as the target. If no project directory is given, default to the current working directory.
--dry-run:
~/.claude/skills/afx-cicd-scaffold/afx-cicd-scaffold.sh init /path/to/project --dry-run
--no-db-migration if they do not use a database):
~/.claude/skills/afx-cicd-scaffold/afx-cicd-scaffold.sh init /path/to/project
cd.ymlIf .github/workflows/ already exists:
--force.--force.When the script runs interactively, it prompts whether to include database-migration.yml. The user can suppress the prompt with --no-db-migration. If the session is non-interactive (piped), the migration file is skipped by default.
All are documented inline in the generated file headers. Key ones for cd.yml:
| Name | Type | Description |
|---|---|---|
AWS_ROLE_ARN_STAGING | Secret | OIDC role ARN for staging: arn:aws:iam::<acct>:role/<project>-gha-deploy-staging |
AWS_ROLE_ARN_PROD | Secret | OIDC role ARN for production: arn:aws:iam::<acct>:role/<project>-gha-deploy-prod |
STAGING_URL | Secret | Base URL for staging smoke tests |
PROD_URL | Secret | Base URL for production smoke tests |
AWS_REGION | Variable | AWS region (e.g. us-east-1) |
ECR_REPOSITORY | Variable | ECR repository name |
ECS_SERVICE | Variable | ECS service name |
ECS_CLUSTER_STAGING | Variable | ECS cluster name for staging |
ECS_CLUSTER_PROD | Variable | ECS cluster name for production |
1.0.0 (ticket 12.2)
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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
日本語の概要は準備中です。原文の説明を表示しています。