git-workflows
90
project-knowledge
Load project architecture and structure knowledge. Use when you need to understand how this project is organized.
aiskillstore
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
git-workflows
90
pr-prepare
Prepare pull request descriptions following project template. Activates on: prepare PR, create PR, pull request, ready for PR, draft PR, write PR
aiskillstore
devops
git-workflows
90
commit-message-generator
Generate appropriate commit messages based on Git diffs
aiskillstore
devops
git-workflows
90
global-conventions
Follow project-wide development conventions including project structure, version control practices, environment configuration, documentation, dependency management, and code review processes. Use this skill when organizing files/directories, writing commit messages, managing branches, configuring environments, handling secrets, maintaining documentation, or establishing team workflows. Apply when working with project structure, README files, .gitignore, environment variables, dependency files (package.json, requirements.txt), feature flags, changelogs, or any aspect of project organization and team collaboration that requires consistency across the development lifecycle.
aiskillstore
devops
git-workflows
90
env-config
Use when setting up environment configuration, loading .env files, or managing application settings across environments. Triggers for: .env setup, loading environment variables, Pydantic BaseSettings, configuration validation, or secret management. NOT for: code-specific logic, feature flags, or runtime feature toggles.
aiskillstore
devops
git-workflows
90
waterfall-development
Enforces strict waterfall development workflow with phase gates. Use when (1) features.yml exists in project root, (2) user asks to implement/develop/build a feature, (3) user explicitly requests waterfall workflow. Creates features.yml if missing when invoked.
aiskillstore
devops
git-workflows
90
high-quality-commit
コード変更を適切なgitコミット戦略でgit commitします。基本的には既存のgitコミットへのsquash戦略を採用し、必要に応じてブランチ全体のgitコミット履歴を再構成します。実装完了時やユーザーがgit commitを依頼した時に使用します。
aiskillstore
devops
git-workflows
90
rust-development
Rust development best practices for the Guts project - idiomatic code, error handling, async patterns, and commonware integration
aiskillstore
devops
git-workflows
90
spec-discovery
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
aiskillstore
devops
git-workflows
90
research-merge
Processes research branches from Claude Code Web sessions - merges content, moves docs to docs/research/, and creates GitHub issues. Use when /popkit:next detects research branches or when manually processing research from mobile sessions. Do NOT use for regular feature branches - only for branches matching claude/research-* or containing research documentation.
aiskillstore
devops
git-workflows
90
senior-rust-practices
This skill should be used when the user asks about "rust workspace", "rust best practices", "cargo workspace setup", "rust code organization", "rust dependency management", "rust testing strategy", "rust project", "scalable rust", "rust CI setup", or needs guidance on senior-level Rust development patterns, workspace design, code organization strategies, or production-ready Rust architectures.
aiskillstore
devops
git-workflows
90
file-boundaries
Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.
aiskillstore
devops
git-workflows
90
ghe-checkpoint
POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread. USE THIS SKILL WHEN: - User says "post a checkpoint", "save my progress", or "save checkpoint" - User completed a milestone and wants to record it - User encountered a blocker and wants to document it - User is about to take a break and wants to save state - Meaningful state change occurred during work PRECONDITION: User must already have an active (claimed, in-progress) thread. DO NOT USE THIS SKILL WHEN: - User wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to FINISH current phase and MOVE to next (use ghe-transition) - No active thread exists (must claim first) EXAMPLES: - User: "Post a checkpoint" → Use ghe-checkpoint - User: "Save my progress, I finished the authentication module" → Use ghe-checkpoint - User: "I need to stop for now, save my work" → Use ghe-checkpoint
aiskillstore
devops
git-workflows
90
finishing-a-development-branch
Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.
aiskillstore
devops
git-workflows
90
conflict-resolver
Smart git merge conflict resolution with context analysis, pattern detection, and automated resol...
aiskillstore
devops
git-workflows
90
when-reviewing-github-pr-use-github-code-review
Comprehensive GitHub pull request code review using multi-agent swarm with specialized reviewers for security, performance, style, tests, and documentation. Coordinates security-auditor, perf-analyzer, code-analyzer, tester, and reviewer agents through mesh topology for parallel analysis. Provides detailed feedback with auto-fix suggestions and merge readiness assessment. Use when reviewing PRs, conducting code audits, or ensuring code quality standards before merge.
aiskillstore
devops