codecleanup
This should only be done if the user asks to "clean up code". At the end of a major change on a git branch this document describes the code clean up tasks that should be performed.
This should only be done if the user asks to "clean up code". At the end of a major change on a git branch this document describes the code clean up tasks that should be performed.
Initialize project context for optimal Claude Code sessions. Use when setting up a new project or documenting an existing (brownfield) project's architecture, tech stack, conventions, and key patterns.
Use when the user explicitly asks for a SKILL to create a worktree. If the user does not mention "skill" or explicitly request skill invocation, do NOT trigger this. Only use when user says things like "use a skill to create a worktree" or "invoke the worktree skill". Creates isolated git worktrees with parallel-running configuration.
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
foundational definitions for GitHub skills, safety rules, tool escalation, and security boundaries
Sync Nushell configuration files between the repo (os-config/nushell) and the system config path ($nu.config-path). Use when the user wants to push, pull, or diff nushell config files.
Use when Codex must inspect or update GitHub resources (issues, PRs, workflows) through the official remote GitHub MCP server.
Rust development best practices, patterns, and conventions. Use when writing Rust code, reviewing .rs files, discussing ownership, lifetimes, borrowing, or Cargo configuration. Triggers on mentions of Rust, Cargo, ownership, borrowing, lifetimes, traits, async Rust, tokio.
Use when asked to review a PR, propose review comments, or prepare a merge checklist.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
Creates a git commit following the project's commit message format specified in INSTRUCTIONS.md.
Git version control workflows, branching strategies, and best practices. Use when discussing git commands, branching, merging, rebasing, or version control workflows. Triggers on mentions of git, branch, merge, rebase, commit, pull request, GitHub, GitLab, version control.
Generates clear commit messages from jj diffs. Use when writing commit messages or reviewing staged changes.
Conventional commit format, type selection, and commit best practices
Summarize code changes on the current git branch (including uncommitted changes) and draft a pull request description using a provided template. Use when the user wants a PR description based on git diffs, branch history, and local working tree changes.
Use when completing blog post drafts with story sections - systematically analyzes commit history to write Context, Challenge, Solution, and Learned sections without making unverified assumptions about business context
Generate LLM-backed release notes between git tags using the repo release-scripts. Use when asked for changelogs, release notes, or summaries between two tags.
Workflow repo ops bằng Serena MCP (tìm file, đọc symbol, chỉnh sửa có kiểm soát) để giảm đọc thừa.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Commits changes with concise, clear commit messages (under 52 characters). Automatically creates feature branches when committing from main/master branches, using simple names like 'johnmog-area-change'. Use when you want to commit changes with a meaningful message or need to safely work off main.
Creates commits strictly following Conventional Commits format. ALWAYS read BEFORE committing changes, amending commits, or when the user mentions git commits, conventional commits, or commit messages.