Git & Version Control

Diagnoses and fixes CI/CD pipeline failures. Use when user mentions 'CI', 'GitHub Actions', 'GitLab CI', 'ビルドエラー', 'テスト失敗', 'パイプライン', 'CIが落ちた', or asks to analyze build/test failures. 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 using git-workspace-review context. Triggers: version bump, semver, release version, changelog update, version update, package version, release preparation Use when: bumping project versions, updating changelogs, preparing releases, coordinating version changes across files DO 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 commit Use when: generating commit messages in conventional commits format DO NOT use when: full PR preparation - use pr-prep instead.

Design, manage, and evolve digital gardens as living knowledge bases within memory palaces. Triggers: digital garden, knowledge base, linking, note curation, content lifecycle, garden maintenance, bidirectional links, knowledge evolution Use when: managing note collections, creating link structures, maintaining knowledge bases, tending garden health and growth DO 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.

Prepare a pull request by validating the workspace, running quality gates, summarizing changes, and drafting the PR template. Triggers: PR preparation, pull request, quality gates, PR template, PR summary, branch preparation, merge request Use when: preparing PRs for submission, running quality gates, drafting PR descriptions and templates DO NOT use when: reviewing existing PRs - use pr-review instead. DO NOT use when: just generating commit messages - use commit-messages. Use this skill for PR preparation.

Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.

detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

Declarative release readiness checklist that mirrors GitHub checks, deployment issues, and documentation requirements. Triggers: release gates, release readiness, deployment checklist, release review, quality signals, rollout scorecard, QA handshake, deployment gates Use when: preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs DO NOT use when: weekly status updates - use github-initiative-pulse. DO NOT use when: code reviews - use pensive review skills. Standardizes release approvals with GitHub-aware checklists.

Interactive project initialization with git setup, workflows, hooks, and build configuration. Triggers: project setup, initialization, scaffold, bootstrap, new project Use 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, backlog Use when: reviewing features or suggesting new features DO 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 summaries sourced from Minister's tracker data. Triggers: initiative pulse, status report, weekly update, stakeholder briefing, github dashboard, blocker radar, initiative health, program metrics Use when: creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health DO 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 conventions Use when: developing new sanctum skills, refactoring existing skills, ensuring consistency across sanctum workflows, referencing standard patterns DO NOT use directly: this skill is infrastructure for other sanctum skills. Provides reusable patterns consumed by all sanctum git and workspace skills.

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 efficiency Use when: workflow felt slow, confusing, or needs optimization DO 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 budget Use when: session starts (mandatory), prompt sizes spike, tool calls increase, before long-running analyses or massive context loads DO 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)