Create a pull request with full validation. Use when ready to submit work for review.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Run full validation, then create a PR if clean.
/sdlc-core:validate --pre-push
If validation fails, report the issues and stop. Do NOT push or create PR.
Re-verify any test counts cited in the PR body.
--pre-push runs the pytest suite only. If the draft PR body cites results
from integration smokes, E2E suites, soak tests, container tests, or any
other harness outside local-validation.py, re-run those exact suites
in this session and update the counts in the body to match the fresh run.
Example: a PR body saying "266 unit tests, 20/20 container smoke, 8/8
sequential E2E, 18/18 fresh-user-flow" requires pytest tests/ -q,
bash tests/integration/workforce-smoke/run-containers.sh,
bash tests/integration/workforce-smoke/run-e2e.sh, and
bash tests/integration/workforce-smoke/run-fresh-user-flow.sh to all
run this session before the PR is opened.
Session memory of test counts goes stale fast — fixtures grow, assertions drift, environments change. Only numbers you have just observed this session belong in the body. If a suite cannot run in this environment (missing binary, no Docker, etc.), delete the number from the body and say so explicitly rather than leaving a stale figure that cites another machine's result.
If the PR already exists and counts have drifted post-creation, update the body in place rather than closing and recreating:
gh pr edit <number> --body-file <updated-body.md>
Verify required artifacts exist:
docs/feature-proposals/retrospectives/If validation passes, proceed:
git branch -vvgit push -u origin <branch>main unless $ARGUMENTS specifies otherwiseCreate the PR using gh pr create:
gh pr create --title "<short title under 70 chars>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points summarizing the changes>
## Changes
<List of files modified/created>
## Test plan
- [ ] `/sdlc-core:validate --pre-push` passes
- [ ] CI pipeline passes
<additional test steps as needed>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.
日本語の概要は準備中です。原文の説明を表示しています。
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
日本語の概要は準備中です。原文の説明を表示しています。
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
日本語の概要は準備中です。原文の説明を表示しています。
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
日本語の概要は準備中です。原文の説明を表示しています。