Use when starting any task in a project - keeps CLAUDE.md instruction file current with high-level project state, prompts for init if missing, adds reflection todo before work to ensure documentation stays updated
A skill that outlines best practices for using Git in a collaborative development environment, including branching strategies, commit conventions, and pull request workflows.
Manage git worktrees and branches. Use when the user asks to create a worktree, new worktree, create a branch, new branch, switch branches, or work on a new feature.
Create conventional commit messages. Use when committing changes or writing commit messages.
Go-specific library/package development patterns. Use when creating Go libraries, designing public APIs with Go idioms, configuring go.mod, managing module versioning, publishing packages, or writing package documentation. Extends meta-library-dev with Go tooling and ecosystem practices.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Git version control, branching strategies, and collaboration patterns
Gitใณใใใใกใใปใผใธใฎไฝๆใฌใคใใฉใคใณใใณใใใไฝๆๆใ`git commit`ๅฎ่กๆใใพใใฏใฆใผใถใผใใณใใใใกใใปใผใธใฎๆธใๆนใซใคใใฆ่ณชๅใใ้ใซไฝฟ็จใใใๆฅๆฌ่ชใงใฎใณใใใใกใใปใผใธไฝๆใซใผใซใๆไพใ
Gerencia commits automaticos ao final de cada fase do SDLC. Garante que artefatos de cada fase sejam commitados e rastreados. Use quando: transicao de fase, checkpoint de progresso.
ใณใใใใปใใใทใฅใๅฎ่กใใSkillใdocs/einja/steering/commit-rules.mdใฎใซใผใซใซๅพใใๅๅฒใณใใใใๅฎๆฝใ็ดๆฅๅผใณๅบใๅฏ่ฝ๏ผ็ขบ่ชใใ๏ผใtask-exec็ต็ฑใงใฏ่ชๅๅฎ่ก
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Commits and pushes code changes. Used when work should be committed and/or pushed to Git.
Use when starting open-ended tasks in unfamiliar codebases, before following existing patterns
Generates a Pull Request message in the template format after analyzing the current branch changes.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
ใใณใใฌใผใๅๆในใญใซใyellow-seed/template ใฎๆดๆฐใไปใฎใชใใธใใชใซๅๆ ใUse when: ใใณใใฌใผใๆดๆฐใฎๅๆ ใtemplateๅๆใๆขๅญใชใใธใใชใธใฎๅคๆด้ฉ็จใไพ้ ผใใใๆใ
GitHub Issue ใไฟฎๆญฃใใในใญใซใ ไปฅไธใฎ็ถๆณใงไฝฟ็จ: (1) ใฆใผใถใผใใIssue #XX ใไฟฎๆญฃใใฆใใจไพ้ ผใใๆ (2) ใฆใผใถใผใๆ็คบ็ใซใ/gh-issue-fixerใใๅฎ่กใใๆ (3) GitHub Issue ใฎๅฏพๅฟใๆฑใใใใๆ
Handles re-reviews after new commits. Use when a PR already has review comments or when responding to developer changes.
The agent implements stacked diffs (stacked PRs) for breaking large changes into reviewable chunks. Use when working on complex features, managing dependent changes, or optimizing code review flow.
Guidelines for creating high-quality Freenet pull requests. This skill should be used when creating PRs for freenet-core, freenet-stdlib, or related repositories. Emphasizes quality over speed, thorough testing, and proper review process.
Git workflow guidelines for AI agents working on this repository
Git Worktreeใไฝฟใฃใ้็บใใญใผใPRไฝๆใCI็ฃ่ฆใใใผใธๆ้ ใworktreeใPRใใใผใธใCIใใใฉใณใไฝๆๆใซไฝฟ็จใ
Detect whether the current project uses jj (Jujutsu) or git for version control. Run this BEFORE any VCS command to use the correct tool.
