## Summary
- Added YAML frontmatter with name and description fields to all 5 skill files
- This enables Claude Code to automatically discover and load skills
- Each skill now has proper metadata for semantic matching
## Affected Files
- skills/gitea/SKILL.md
- skills/code-review/SKILL.md
- skills/issue-writing/SKILL.md
- skills/backlog-grooming/SKILL.md
- skills/roadmap-planning/SKILL.md
## Test Plan
- [ ] Restart Claude Code
- [ ] Verify skills appear in discovered skills list
- [ ] Test that skills are invoked when relevant context is detected
Closes #12
Skills require YAML frontmatter with name and description fields
for Claude Code to automatically discover and load them. Added
frontmatter to all five skill files:
- gitea: CLI for issues, PRs, and repository management
- code-review: Guidelines for reviewing code changes
- issue-writing: How to write clear, actionable issues
- backlog-grooming: Review and improve existing issues
- roadmap-planning: Plan features and create issues
Closes#12🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This is an automated review generated by the code-reviewer agent.
Summary
This PR adds YAML frontmatter to all 5 skill files to enable automatic discovery by Claude Code. The changes are minimal, focused, and correctly implemented.
Findings
Code Quality
Clean, minimal changes - adds only the necessary frontmatter without modifying existing content
Consistent formatting across all files
Well-structured YAML with proper key-value pairs
Potential Bugs
No issues found
YAML frontmatter is properly formatted and should parse correctly
YAML Frontmatter Format
Correctly uses triple-dash delimiters (---) to open and close YAML blocks
Proper key-value syntax with name and description fields
Name fields use kebab-case matching the directory names (backlog-grooming, code-review, gitea, issue-writing, roadmap-planning)
Description fields are clear, concise, and accurately describe each skill's purpose
Appropriate blank line between frontmatter and markdown content
Consistency Across All Skill Files
All 5 files follow identical structure:
YAML frontmatter at the top
Blank line separator
Original markdown heading
Naming convention is consistent: directory name = frontmatter name field
Description style is consistent: imperative/instructional tone
No deviations or anomalies between files
Style Notes
Formatting is clean and consistent with markdown best practices
Descriptions are informative without being verbose
The kebab-case naming convention is appropriate for skill identifiers
Test Coverage
Changes are declarative YAML metadata - no logic to test
Recommended manual verification after merge:
Restart Claude Code
Verify skills appear in discovered skills list
Test that skills are invoked when relevant context is detected
Verdict
LGTM
This PR correctly implements YAML frontmatter for all skill files with perfect consistency and proper formatting. The changes enable automatic skill discovery without modifying any existing functionality. Ready to merge.
## AI Code Review
> This is an automated review generated by the code-reviewer agent.
### Summary
This PR adds YAML frontmatter to all 5 skill files to enable automatic discovery by Claude Code. The changes are minimal, focused, and correctly implemented.
### Findings
#### Code Quality
- Clean, minimal changes - adds only the necessary frontmatter without modifying existing content
- Consistent formatting across all files
- Well-structured YAML with proper key-value pairs
#### Potential Bugs
- No issues found
- YAML frontmatter is properly formatted and should parse correctly
#### YAML Frontmatter Format
- Correctly uses triple-dash delimiters (`---`) to open and close YAML blocks
- Proper key-value syntax with `name` and `description` fields
- Name fields use kebab-case matching the directory names (backlog-grooming, code-review, gitea, issue-writing, roadmap-planning)
- Description fields are clear, concise, and accurately describe each skill's purpose
- Appropriate blank line between frontmatter and markdown content
#### Consistency Across All Skill Files
- All 5 files follow identical structure:
- YAML frontmatter at the top
- Blank line separator
- Original markdown heading
- Naming convention is consistent: directory name = frontmatter name field
- Description style is consistent: imperative/instructional tone
- No deviations or anomalies between files
#### Style Notes
- Formatting is clean and consistent with markdown best practices
- Descriptions are informative without being verbose
- The kebab-case naming convention is appropriate for skill identifiers
#### Test Coverage
- Changes are declarative YAML metadata - no logic to test
- Recommended manual verification after merge:
- Restart Claude Code
- Verify skills appear in discovered skills list
- Test that skills are invoked when relevant context is detected
### Verdict
**LGTM**
This PR correctly implements YAML frontmatter for all skill files with perfect consistency and proper formatting. The changes enable automatic skill discovery without modifying any existing functionality. Ready to merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Affected Files
Test Plan
Closes #12
AI Code Review
Summary
This PR adds YAML frontmatter to all 5 skill files to enable automatic discovery by Claude Code. The changes are minimal, focused, and correctly implemented.
Findings
Code Quality
Potential Bugs
YAML Frontmatter Format
---) to open and close YAML blocksnameanddescriptionfieldsConsistency Across All Skill Files
Style Notes
Test Coverage
Verdict
LGTM
This PR correctly implements YAML frontmatter for all skill files with perfect consistency and proper formatting. The changes enable automatic skill discovery without modifying any existing functionality. Ready to merge.