Git & Version Control

This skill should be used when the user asks about "game architecture", "design patterns", "manager pattern", "singleton pattern", "ScriptableObject", "ScriptableObject architecture", "event system", "Observer pattern", "pub-sub", "MVC in Unity", "dependency injection", "service locator", or needs guidance on structuring Unity projects and game systems.

Use when automating browsers with Playwright/Puppeteer, testing Chrome extensions, using Chrome DevTools Protocol (CDP), handling dynamic content/SPAs, or debugging automation issues

Comprehensive guide for modern front-end testing with Playwright (2025). This skill should be used when writing end-to-end tests, component tests, or visual regression tests for web applications using Playwright. Covers Page Object Model patterns, TypeScript integration, modern SPA testing strategies, accessibility testing, and CI/CD automation with GitHub Actions.

Use this skill when implementing combat automation in SND macros using the BossModReborn plugin. Covers preset management, rotation configuration, and AI control via chat commands.

Post-session analysis agent that extracts learnings, decisions, user preferences, and "surprise moments" from conversation transcripts. Stores insights in Memory Lane with vector embeddings for future retrieval.

git 명령어 사용 및 커밋 생성 가이드

Generate conventional commit messages following best practices. Use when creating structured git commit messages.

Interpretive guidance for Python code quality using ruff (modern) or pylint+isort+black (traditional). Use when linting Python files, configuring Python tools, troubleshooting lint errors, or understanding tool selection.

Draft and review Git commits and commit messages with an emphasis on atomic change sets and clean history. Use when asked to commit changes, propose commit messages, split/squash/rebase commits, or clean up a branch via fixup commits and interactive rebase/autosquash.

Create pull request from current branch with AI-generated title and description.Use when user wants to create a PR for their current branch. Triggers include:- Korean: "PR 만들어줘", "PR 생성해줘", "풀 리퀘스트 만들어줘"- English: "create PR", "open PR", "make pull request"- Context: User has commits on current branch and wants to open PR

Git 저장소의 변경사항을 추적하고 요약합니다. 미커밋 코드, 최근 커밋, 커밋 히스토리를 확인할 때 사용하세요. catchup, 변경사항, git diff, 커밋 히스토리, 작업 내용 파악 등의 키워드에 반응합니다.

Comment on GitHub issues using the gh CLI. Use when Codex needs to share an implementation plan, progress update, or blockers. Always read the issue body and comments for context, optionally read related issues, and only create or update Codex-owned comments.

Use when monitoring code quality over time, measuring refactoring impact, tracking if complexity is improving or worsening, or validating technical debt work - tracks complexity metrics across git history identifying improving, stable, or deteriorating files

Efficient PR creation with gh CLI - automated branch, commit, push, and pr-create. Use when user asks to "create PR", "open pull request", or "make PR".

Creates README.md navigation maps for agent consumption. README IS the map - no human READMEs exist. Use when mapping directories, creating navigation structures, or preparing codebases for agentic workflows.

Run quality checks and create properly formatted git commits. Use before committing code to ensure quality standards are met and commit messages follow project conventions.

Retrieve GitHub user profile and repository information using the gh CLI tool. Use when the user asks about their GitHub profile, statistics, repositories, or wants to view their GitHub information. Examples: Show me my GitHub profile, What are my top repositories, Get my GitHub stats.

Collect git info and prepare PR content for reedom-gh:pr-maker agent.

Git conventions for commits, branches, and pull requests. Conventional commit format and PR workflows.

Optimizes GitHub Actions CI/CD workflows through test sharding, intelligent caching, and workflow parallelization. Use when CI execution time exceeds limits, costs are too high, or workflows need parallelization.