Improve skill descriptions and documentation

Updated all skill descriptions with proper trigger terms following
the pattern: "What it does. Use when [trigger terms]."

Skills updated:
- code-review: triggers on PR review, code quality, bugs, security
- issue-writing: triggers on creating issues, bug reports, features
- backlog-grooming: triggers on grooming, reviewing issue quality
- roadmap-planning: triggers on planning features, breaking down work

Updated docs/writing-skills.md:
- Added YAML frontmatter requirements section
- Documented required and optional fields
- Added guidance on writing effective descriptions
- Updated "How Skills are Loaded" to reflect model-invoked behavior
- Added note about subagent skill access
- Updated checklist with frontmatter requirements
- Added reference to official documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-01 10:30:04 +01:00
parent d16332e552
commit 98796ba537
5 changed files with 100 additions and 32 deletions

View File

@@ -1,6 +1,6 @@
---
name: backlog-grooming
description: How to review and improve existing issues for clarity and actionability
description: Review and improve existing issues for clarity and actionability. Use when grooming the backlog, reviewing issue quality, cleaning up stale issues, or when the user wants to improve existing issues.
---
# Backlog Grooming

View File

@@ -1,6 +1,6 @@
---
name: code-review
description: Guidelines and templates for reviewing code changes in pull requests
description: Review code for quality, bugs, security, and style issues. Use when reviewing pull requests, checking code quality, looking for bugs or security vulnerabilities, or when the user asks for a code review.
---
# Code Review

View File

@@ -1,6 +1,6 @@
---
name: issue-writing
description: How to write clear, actionable issues with proper structure and acceptance criteria
description: Write clear, actionable issues with proper structure and acceptance criteria. Use when creating issues, writing bug reports, feature requests, or when the user needs help structuring an issue.
---
# Issue Writing

View File

@@ -1,6 +1,6 @@
---
name: roadmap-planning
description: How to plan features and create issues for implementation
description: Plan features and break down work into implementable issues. Use when planning a feature, creating a roadmap, breaking down large tasks, or when the user needs help organizing work into issues.
---
# Roadmap Planning