Use @ file references to include skills in commands
Skills have only ~20% auto-activation rate when referenced by name. Using @~/.claude/skills/*/SKILL.md guarantees skill content is loaded. Updated all commands to use file references instead of "Use the X skill". Updated docs/writing-commands.md with new pattern and examples. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -5,7 +5,7 @@ argument-hint: [title] or "batch"
|
||||
|
||||
# Create Issue(s)
|
||||
|
||||
Use the gitea skill.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
## Single Issue (default)
|
||||
If title provided, create an issue with that title and ask for description.
|
||||
|
||||
@@ -4,7 +4,7 @@ description: Show dashboard of open issues, PRs awaiting review, and CI status.
|
||||
|
||||
# Repository Dashboard
|
||||
|
||||
Use the gitea skill.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
Fetch and display:
|
||||
1. All open issues
|
||||
|
||||
@@ -5,7 +5,9 @@ argument-hint: [issue-number]
|
||||
|
||||
# Groom Issues
|
||||
|
||||
Use the gitea, backlog-grooming, and issue-writing skills.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
@~/.claude/skills/backlog-grooming/SKILL.md
|
||||
@~/.claude/skills/issue-writing/SKILL.md
|
||||
|
||||
## If issue number provided ($1):
|
||||
|
||||
|
||||
@@ -5,7 +5,9 @@ argument-hint: <feature-description>
|
||||
|
||||
# Plan Feature: $1
|
||||
|
||||
Use the gitea, roadmap-planning, and issue-writing skills.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
@~/.claude/skills/roadmap-planning/SKILL.md
|
||||
@~/.claude/skills/issue-writing/SKILL.md
|
||||
|
||||
1. **Understand the feature**: Analyze what "$1" involves
|
||||
2. **Explore the codebase** if needed to understand context
|
||||
|
||||
@@ -5,7 +5,7 @@ argument-hint: <pr-number>
|
||||
|
||||
# Review PR #$1
|
||||
|
||||
Use the gitea skill.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
1. **View PR details** including description and metadata
|
||||
2. **Get the diff** to review the changes
|
||||
|
||||
@@ -4,7 +4,7 @@ description: View current issues as a roadmap. Shows open issues organized by st
|
||||
|
||||
# Roadmap View
|
||||
|
||||
Use the gitea skill.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
1. **Fetch all open issues**
|
||||
2. **Analyze dependencies** from issue descriptions
|
||||
|
||||
@@ -5,7 +5,7 @@ argument-hint: <issue-number>
|
||||
|
||||
# Work on Issue #$1
|
||||
|
||||
Use the gitea skill.
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
1. **View the issue** to understand requirements
|
||||
2. **Create a branch**: `git checkout -b issue-$1-<short-kebab-title>`
|
||||
|
||||
Reference in New Issue
Block a user