Merge pull request #2 from itk-dev/feature/add-github-workflow-skill

feat: add itk-dev-github workflow skill

Author: yepzdk

README.md

@@ -12,6 +12,8 @@ itkdev-claude-plugins/
 ├── .mcp.json                   # MCP server configurations
 ├── commands/                   # Slash commands (Markdown files)
 │   └── example.md
+├── skills/                     # Skills (Markdown files with frontmatter)
+│   └── itk-dev-github.md
 └── README.md
 ```
 
@@ -33,6 +35,16 @@ Team members can install the marketplace and plugins with:
 
 Browser feedback collection tool from [mcp-claude-code-browser-feedback](https://github.com/itk-dev/mcp-claude-code-browser-feedback).
 
+## Included Skills
+
+### itk-dev-github
+
+GitHub workflow guidelines for the ITK Dev team. Automatically activates when working with Git, branches, commits, or pull requests. Covers:
+- Branch naming conventions (`feature/issue-{number}-{description}`)
+- Conventional commit messages
+- Changelog updates (Keep a Changelog format)
+- PR requirements and templates
+
 ## Adding New Tools
 
 ### Adding MCP Servers
@@ -53,3 +65,18 @@ Edit `.mcp.json` to add new MCP server configurations:
 ### Adding Commands
 
 Create new Markdown files in the `commands/` directory. Each file becomes a slash command.
+
+### Adding Skills
+
+Create new Markdown files in the `skills/` directory with YAML frontmatter:
+
+```markdown
+---
+name: skill-name
+description: When this skill should be activated automatically.
+---
+
+# Skill Content
+
+Your skill instructions here...
+```

commands/example.md

@@ -1,6 +1,6 @@
 # Example Command
 
-This is an example slash command for the team-tools plugin.
+This is an example slash command for the itkdev-tools plugin.
 
 ## Usage
 

skills/itk-dev-github.md

@@ -0,0 +1,80 @@
+---
+name: itk-dev-github
+description: GitHub workflow guidelines for itk-dev team. Use when working with Git, creating branches, making commits, opening pull requests, or any GitHub-related development tasks. Ensures compliance with team conventions for branching, commits, changelogs, and PR workflows.
+---
+
+# itk-dev GitHub Workflow
+
+## Core Rules
+
+1. **Never commit directly to main** - All changes go through pull requests
+2. **Always create a feature branch** for every PR
+3. **Every PR must include** an updated CHANGELOG and reference related GitHub issues
+4. **Close related issues** upon PR merge using "Closes #XX" syntax
+
+## Branch Naming
+
+Format: `feature/issue-{number}-{short-description}`
+
+Examples:
+- `feature/issue-123-add-user-authentication`
+- `feature/issue-45-fix-pagination-bug`
+- `feature/issue-78-update-api-endpoints`
+
+## Commit Messages
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+<type>: <description>
+
+[optional body]
+
+[optional footer]
+```
+
+Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `perf`, `ci`, `build`
+
+Examples:
+- `feat: add language switcher component`
+- `fix: resolve pagination offset error`
+- `docs: update API documentation`
+- `refactor: extract validation logic to service`
+
+## Changelog
+
+Follow [Keep a Changelog](https://keepachangelog.com/) format. Update `CHANGELOG.md` with every PR under the `[Unreleased]` section.
+
+Categories: `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`
+
+## Pull Request Requirements
+
+### Before Opening PR
+- [ ] All GitHub Actions checks pass
+- [ ] CHANGELOG.md updated under `[Unreleased]`
+- [ ] Branch is up-to-date with main
+
+### PR Description Template
+
+```markdown
+## Summary
+Brief description of what this PR does and which issue it addresses (#XX).
+
+## Features Added
+* Feature 1: Description
+* Feature 2: Description
+
+## Files Changed
+* `path/to/file.ext` - What changed
+* `path/to/new-file.ext` (new) - Purpose
+
+## Test Plan
+* Step-by-step verification instructions
+* Expected outcomes for each test
+
+Closes #XX
+```
+
+### Review Requirements
+- Minimum **one approving review** required before merge
+- All GitHub Actions checks must pass