ai-assisted-operations
AI-powered issue operations via gh-models. TRIGGERS - issue summarization, auto-labeling, issue insights.
Best use case
ai-assisted-operations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
AI-powered issue operations via gh-models. TRIGGERS - issue summarization, auto-labeling, issue insights.
Teams using ai-assisted-operations should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ai-assisted-operations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ai-assisted-operations Compares
| Feature / Agent | ai-assisted-operations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
AI-powered issue operations via gh-models. TRIGGERS - issue summarization, auto-labeling, issue insights.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AI-Powered Issue Operations
**Capability:** AI-assisted issue summarization, auto-labeling, Q&A, and documentation generation using gh-models
**When to use:** Leveraging LLMs for intelligent issue processing and automation
**Installation Required:** `gh extension install github/gh-models`
---
## Quick Start
### List Available Models
```bash
# Show all 29+ models
gh models list
# Popular models for issue operations:
# - openai/gpt-4.1
# - openai/gpt-4o-mini
# - anthropic/claude-3.5-sonnet
```
### Basic Usage
```bash
# Run AI model
gh models run "openai/gpt-4.1" "Your prompt here"
# With multi-line prompt
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Analyze this issue and suggest improvements:
- Title clarity
- Completeness
- Priority assessment
EOF
)"
```
---
## Common Workflows
### 1. Issue Summarization (88% effectiveness)
```bash
# Get issue content
ISSUE_BODY=$(gh issue view 123 --json body --jq .body)
# Summarize
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Summarize this issue in 2-3 bullet points:
$ISSUE_BODY
EOF
)"
```
**Use Case:** Creating concise summaries for long issues, weekly reports
---
### 2. Auto-Label Suggestion (89% effectiveness)
```bash
# Get issue content
ISSUE_CONTENT=$(gh issue view 123 --json title,body --jq '{title, body}')
# Available labels
LABELS="bug,feature,documentation,question,enhancement,wontfix,duplicate"
# Suggest labels
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Suggest 2-3 labels from this list: $LABELS
Issue:
$ISSUE_CONTENT
Respond with comma-separated label names only.
EOF
)"
# Apply suggested labels
gh issue edit 123 --add-label bug,priority:high
```
**Use Case:** Automating issue triage, maintaining consistent labeling
---
### 3. Issue Q&A (91% effectiveness)
```bash
# Knowledge base Q&A
QUERY="How do I use Claude Code plan mode?"
# Search relevant issues
ISSUES=$(gh search issues "$QUERY" --repo=terrylica/claude-code-skills-github-issues --json number,title,body --jq '.')
# Ask AI
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Answer this question based on these GitHub Issues:
Question: $QUERY
Issues:
$ISSUES
Provide a concise answer with issue references.
EOF
)"
```
**Use Case:** Knowledge base Q&A, finding relevant information across issues
---
### 4. Documentation Generation (86% effectiveness)
```bash
# Get related issues
ISSUES=$(gh search issues --label=feature-request --closed --json title,body --jq '.')
# Generate changelog
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Generate a user-facing changelog from these closed feature requests:
$ISSUES
Format:
## New Features
- Feature name: Brief description
Keep it concise and user-friendly.
EOF
)"
```
**Use Case:** Generating changelogs, release notes, feature documentation
---
### 5. Issue Classification
```bash
# Get issue
ISSUE=$(gh issue view 123 --json title,body --jq '{title, body}')
# Classify
gh models run "openai/gpt-4.1" "$(cat <<'EOF'
Classify this issue into ONE category:
- Bug Report
- Feature Request
- Documentation
- Question
- Enhancement
Issue:
$ISSUE
Respond with category name only.
EOF
)"
```
---
## Effectiveness Metrics (Empirical Testing)
| Operation | Effectiveness | Test Count |
| ------------------------ | ------------- | ---------- |
| Issue Summarization | 88% | 5 tests |
| Auto-Label Suggestion | 89% | 5 tests |
| Issue Q&A | 91% | 5 tests |
| Documentation Generation | 86% | 5 tests |
| Issue Classification | 88% | 5 tests |
**Average Effectiveness: 88%**
**Detailed Results:** [GH-MODELS-POC-RESULTS.md](/docs/testing/GH-MODELS-POC-RESULTS.md)
---
## Model Selection
**Fast & Cheap (Good for bulk operations):**
- `openai/gpt-4o-mini` - Fast, cost-effective
- `openai/gpt-3.5-turbo` - Balanced
**High Quality (Complex analysis):**
- `openai/gpt-4.1` - Best quality
- `anthropic/claude-3.5-sonnet` - Long context, detailed analysis
**Testing:** Try different models to find best quality/cost tradeoff
---
## Best Practices
1. **Test prompts first** - Verify output quality before automation
2. **Provide context** - Include relevant labels, repo info in prompt
3. **Be specific** - Clear instructions = better results
4. **Iterate** - Refine prompts based on output quality
5. **Validate output** - AI can make mistakes, always verify
6. **Rate limits** - Be aware of API rate limits for batch operations
---
## Limitations
- **API rate limits** - Check GitHub API limits for your account
- **Cost** - Some models have usage costs
- **Accuracy** - Not 100% reliable, human review recommended
- **Context size** - Very long issues may hit token limits
- **No state** - Each call is independent, no conversation memory
---
## Integration Example: Auto-Triage Workflow
```bash
#!/bin/bash
# Auto-triage new issues
# Get new issues
gh issue list --label needs-triage --json number,title,body --jq '.[] | @json' | \
while read -r issue; do
# Extract fields
number=$(echo "$issue" | jq -r .number)
content=$(echo "$issue" | jq -r '{title, body}')
# Get AI suggestions
labels=$(gh models run "openai/gpt-4o-mini" "$(cat <<EOF
Suggest 2-3 labels: bug,feature,documentation,question,enhancement
Issue: $content
Respond with comma-separated labels only.
EOF
)")
# Apply labels
gh issue edit "$number" --add-label "$labels" --remove-label needs-triage
echo "Triaged issue #$number: $labels"
done
```
---
**Installation:** `gh extension install github/gh-models`
**Full Extension Guide:** [GITHUB_CLI_EXTENSIONS.md](/docs/research/GITHUB_CLI_EXTENSIONS.md)
**Complete POC Results:** [GH-MODELS-POC-RESULTS.md](/docs/testing/GH-MODELS-POC-RESULTS.md)Related Skills
u01482-constraint-compilation-for-healthcare-operations
Operate the "Constraint Compilation for healthcare operations" capability in production for healthcare operations workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
Operations & Growth Expert
专注于内容创作(文案、运营稿件)、运营数据分析、以及营销活动策划与设置。帮助项目实现从“可用”到“好用”及“增长”的闭环。
async-operations
Specifies the preferred syntax for asynchronous operations using async/await and onMount for component initialization. This results in cleaner and more readable asynchronous code.
search-operations
Search GitHub - find code, issues, users, and repositories across GitHub using gh CLI
Sales Operations Automation
* **Depends on**: None * **Compatible with**: None * **Conflicts with**: None * **Related Skills**: None # Sales Operations Automation
aliyun-operations
阿里云服务器运维操作。包括ECS实例管理、安全组配置、服务部署、日志查看。适用于服务器管理、端口开放、应用部署等任务。
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
accessibility-ux-audit
Audit and enhance accessibility and UX across all pages and components.
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
accessibility-planning
Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.
accessibility-design
WCAG 2.1 AA compliance patterns, screen reader compatibility, keyboard navigation, and ARIA best practices. Use when implementing accessible interfaces, reviewing UI components, or auditing accessibility compliance. Covers semantic HTML, focus management, color contrast, and assistive technology testing.