Package source files into plugin directories using release-mapping.yaml. Use when preparing a plugin release.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Package source files into plugin directories based on release-mapping.yaml.
patch — Bump patch version (0.1.0 → 0.1.1). Default if no argument.minor — Bump minor version (0.1.0 → 0.2.0).major — Bump major version (0.1.0 → 1.0.0).Read release-mapping.yaml from the repository root. This file defines which source files map to which plugin directories.
For each plugin in the mapping, process each component type:
Skills — for each skill entry:
skills/validate/SKILL.md)plugins/<plugin>/skills/<skill-name>/SKILL.mdskills/validate/SKILL.md → skills/validate/SKILL.md)Agents — for each agent entry:
agents/core/sdlc-enforcer.md)plugins/<plugin>/agents/<filename>Scripts — for each script entry:
plugins/sdlc-core/scripts/session-banner.sh)plugins/<plugin>/scripts/<filename>validate skill, not via wrapper scripts. Only hook-invoked scripts (e.g., session-banner.sh, check-tmp-usage.py) belong here.Hooks — hooks are plugin-native, no copy needed (they reference ${CLAUDE_PLUGIN_ROOT})
Bump version in each non-stub plugin's plugin.json:
.claude-plugin/plugin.json.claude-plugin/marketplace.json (at the repo root) for this pluginValidate the result:
plugin.json is valid JSON for each pluginReport what was packaged:
Release packaged:
sdlc-core v0.1.1:
Skills: 7 (validate, new-feature, commit, pr, rules, setup-team, release-plugin)
Agents: 3 (sdlc-enforcer, critical-goal-reviewer, code-review-specialist)
Scripts: 6
Hooks: 1
Stub plugins unchanged:
sdlc-team-ai (0.1.0-stub)
sdlc-team-fullstack (0.1.0-stub)
...
Next steps:
1. Review changes: git diff plugins/
2. Commit: git add plugins/ && git commit -m "release: sdlc-core v0.1.1"
3. Tag for stable: git tag v0.1.1
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。