Git 與版本控制

Sets up new projects and generates workflow files like CLAUDE.md, AGENTS.md, Plans.md. Use when user mentions セットアップ, setup, 初期化, initialize, 新規プロジェクト, ワークフローファイル生成. Do NOT load for: 実装作業, レビュー, ビルド検証, デプロイ.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap", "what should we build next", "competitive analysis", "gap analysis", "sync issues", or mentions product management workflows. Provides AI-native PM capabilities for startups with signal-based feature tracking, the WINNING prioritization filter, and GitHub Issues integration with deduplication.

Bump project versions across configs, docs, and changelog usinggit-workspace-review context.Triggers: version bump, semver, release version, changelog update, versionupdate, package version, release preparationUse when: bumping project versions, updating changelogs, preparing releases,coordinating version changes across filesDO NOT use when: just documentation updates - use doc-updates.DO NOT use when: full PR preparation - use pr-prep.Use this skill for version management and release preparation.

Generate conventional commit messages from staged changes with correct type/scope.Triggers: commit message, conventional commit, git commitUse when: generating commit messages in conventional commits formatDO NOT use when: full PR preparation - use pr-prep instead.

Design, manage, and evolve digital gardens as living knowledge bases withinmemory palaces.Triggers: digital garden, knowledge base, linking, note curation, content lifecycle,garden maintenance, bidirectional links, knowledge evolutionUse when: managing note collections, creating link structures, maintainingknowledge bases, tending garden health and growthDO NOT use when: creating memory palace structures - use memory-palace-architect.DO NOT use when: evaluating new knowledge - use knowledge-intake.Consult this skill when cultivating and maintaining digital gardens.

Interactive project initialization with git setup, workflows, hooks, and build configuration.Triggers: project setup, initialization, scaffold, bootstrap, new projectUse when: starting new projects or initializing repositories

Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions.Triggers: feature review, prioritization, RICE, WSJF, roadmap, backlogUse when: reviewing features or suggesting new featuresDO NOT use when: evaluating single feature scope - use scope-guard.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.

Generate program dashboards, GitHub-ready comment digests, and CSV summariessourced from Minister's tracker data.Triggers: initiative pulse, status report, weekly update, stakeholder briefing,github dashboard, blocker radar, initiative health, program metricsUse when: creating status reports, weekly updates, stakeholder briefings,generating GitHub comment digests, tracking initiative healthDO NOT use when: release gates/readiness - use release-health-gates.DO NOT use when: project planning - use spec-kit:speckit-orchestrator.Outputs markdown digests and CSV exports for GitHub issues and PRs.

Shared infrastructure and patterns for sanctum git/workspace skills.Triggers: sanctum patterns, todowrite patterns, git commands, output templates,sanctum infrastructure, shared patterns, git conventionsUse when: developing new sanctum skills, refactoring existing skills,ensuring consistency across sanctum workflows, referencing standard patternsDO NOT use directly: this skill is infrastructure for other sanctum skills.Provides reusable patterns consumed by all sanctum git and workspace skills.

Fix GitHub issues using subagent-driven-development with parallel executionwhere appropriate.Triggers: fix issue, github issue, issue resolution, subagent development,parallel execution, issue workflow, gh issue, fix githubUse when: addressing GitHub issues systematically, multiple related issuesneed fixing, tasks can be parallelized across subagents, quality gates neededbetween task batchesDO NOT use when: single simple fix - just implement directly.DO NOT use when: issue needs clarification - comment first to clarify scope.Uses subagents for parallel execution with code review gates between batches.

Lightweight preflight checklist for verifying repo path, staged changes, anddiffs before other workflows.Triggers: git status, preflight, workspace check, staged changes, diff review,git verification, repo stateUse when: verifying workspace state before other git operations, checkingstaged changes, preflight checks before commits or PRsDO NOT use when: full commit workflow - use commit-messages instead.DO NOT use when: full PR preparation - use pr-prep.Use this skill as foundation for git workflows.

Compose processing stages using a pipes-and-filters model for ETL, mediaprocessing, or compiler-like workloads.Triggers: pipeline architecture, pipes and filters, ETL, data transformation,stream processing, CI/CD pipeline, media processing, batch processingUse when: data flows through fixed sequence of transformations, stages can beindependently developed and tested, parallel processing of stages is beneficialDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: data flow isn't sequential or predictable.DO NOT use when: complex branching/merging logic dominates.Consult this skill when designing data pipelines or transformation workflows.

CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.

Retrospective workflow evaluation and improvement of skills, agents, commands, and hooks.Triggers: workflow improvement, retrospective, workflow efficiencyUse when: workflow felt slow, confusing, or needs optimizationDO NOT use when: implementing features - focus on feature work first.

Minimize token usage through conservative prompting, work delegation,and quota tracking.Triggers: token usage, quota, token limits, prompt size, token conservation,usage tracking, delegation, context compression, token budgetUse when: session starts (mandatory), prompt sizes spike, tool calls increase,before long-running analyses or massive context loadsDO NOT use when: context-optimization already handles the scenario.DO NOT use when: simple queries with minimal context.Use this skill at the START of every session. This is MANDATORY for quota management.

Configure GitHub Actions workflows for CI/CD (test, lint, typecheck, publish)

Update and maintain tests following TDD/BDD principles with detailedquality assurance.Triggers: test updates, test maintenance, test generation, TDD workflow,BDD patterns, test coverage, pytest, test enhancement, quality assuranceUse when: updating existing tests, generating new tests for features,enhancing test quality, ensuring detailed coverage, pre-commit validationDO NOT use when: auditing test suites - use pensive:test-review.DO NOT use when: writing production code - focus on implementation first.Run git-workspace-review first to understand which tests need updates.

Generic template patterns and lifecycle stages for knowledge storage,configuration management, and structured documentation.Triggers: storage templates, lifecycle stages, maturity progression, namingconventions, knowledge storage, configuration templates, documentation patternsUse when: organizing knowledge storage, managing configuration lifecycle,creating structured documentation, establishing naming conventionsDO NOT use when: simple storage without lifecycle or structure needs.Consult this skill when designing storage and documentation systems.