local-development-standard
Standardized local development environment setup ensuring consistency across team members and reducing "works on my machine" issues.
Discover databases git workflows skills, compare source repositories and read the instructions for each workflow.
Standardized local development environment setup ensuring consistency across team members and reducing "works on my machine" issues.
Manage semantic versioning, changelog generation, and release notes. Auto-generates entries from completed issues or git diff.
Standardized commit message formats and conventions for clear, searchable, and automated-friendly version control history.
Standardized development environment configuration including tools, IDE settings, and automation for consistent developer experience.
Development workflow for features, bugs, refactoring. Auto-activates for multi-file implementations.
Single source of truth for repository structure and entry points, including key directories, domain boundaries, shared code, integrations, and build/deploy references
Use when working with Docker containers, creating Dockerfile configurations, writing docker-compose files, setting up CI/CD pipelines with GitHub Actions, or managing infrastructure deployments.
Review changes like a strict backend TL: correctness, edge cases, performance, naming, tests, and operational safety.
Philosophy compliance guardian - ensures code aligns with amplihack's ruthless simplicity, brick philosophy, and Zen-like minimalism through systematic review
Analyze code and documentation, find gaps, update docs. 문서 업데이트, 코드 문서 동기화, 문서 검토.
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
Initialize and configure local development tooling for TypeScript, Rust, and Python projects including monorepos. Use when setting up linting (ESLint, Biome, clippy, ruff), formatting (Prettier, rustfmt, ruff),...
Use when about to run "git stash", encountering modified files you didn't create, or working with git operations that require a clean working tree.
Full GitHub MCP Server parity via gh CLI. Use for ALL GitHub operations: repos, issues, PRs, actions, releases, code security, discussions, notifications, search, users, orgs, gists, projects. ALWAYS use instea...
Create pull request with proper format. PR 생성, 변경사항 분석, PR 메시지 작성.
Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
Use when operating in a repository that contains `.jj/`, when a repository is colocated with `.jj/` and `.git/`, or when the user mentions jj/Jujutsu. Prefer jj workflows over git in jj-managed repositories unl...
Initialize workflow for new empty projects. Creates core memories and directory structure.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when creating a PR, pushing to a feature branch for review, or about to run gh pr create. Covers conflict resolution, PR templates, and merge strategies.
Streamlined bug fixing workflow that creates GitHub issues, writes reproducible tests, finds fixes, and commits changes. Use when a user reports a bug and wants to: (1) Create a GitHub issue, (2) Write a test t...
Contribute skills back to upstream via branch and PR
Create isolated git worktrees with smart directory selection and safety verification
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.