Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Github:Issues

ASecurity

Issue triage - stale issues, blocking, no attention, should-close analysis

302 stars
0 votes
0 copies
0 views
Added 9/20/2026
devopsbashgitsecurity

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add rossoctl/rossoctl --skill github:issues --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github:Issues?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Github:Issues
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rossoctl-github-issues/badge)](https://www.skillsdirectory.com/skills/rossoctl-github-issues)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: github:issues
description: Issue triage - stale issues, blocking, no attention, should-close analysis
---

# Issue Triage

Analyze open issues to identify priority, stale items, and cleanup candidates.

## Variables

Set at session start:

```bash
export OWNER=<org-or-user>
export REPO=<repo-name>
```

## When to Use

- Weekly issue grooming
- Before sprint planning
- When backlog grows too large

> **Auto-approved**: All `gh` commands are read-only and auto-approved.

## Analysis Steps

### 1. All Open Issues

```bash
gh issue list --repo $OWNER/$REPO --state open --limit 100 --json number,title,labels,createdAt,updatedAt,assignees,comments
```

### 2. Issues Without Attention (no assignee, no comments)

```bash
gh issue list --repo $OWNER/$REPO --state open --limit 100 --json number,title,assignees,comments --jq '.[] | select(.assignees | length == 0) | select(.comments == 0) | "#\(.number) \(.title)"'
```

### 3. Stale Issues (no update > 30 days)

```bash
gh issue list --repo $OWNER/$REPO --state open --limit 100 --json number,title,updatedAt --jq '.[] | select(.updatedAt < (now - 30*24*3600 | strftime("%Y-%m-%dT%H:%M:%SZ"))) | "#\(.number) \(.title) (last: \(.updatedAt))"'
```

### 4. Blocking / High Priority

```bash
gh issue list --repo $OWNER/$REPO --state open --label "priority/critical,priority/high,blocking" --json number,title,labels
```

### 5. Security Issues

```bash
gh issue list --repo $OWNER/$REPO --state open --label "security" --json number,title,createdAt
```

## Triage Report

```markdown
## Issue Triage Report

### Needs Attention (no assignee, no comments): N
- [list]

### Stale (> 30 days no activity): N
- [list — consider closing or updating]

### Blocking / High Priority: N
- [list — needs immediate action]

### Candidates to Close
- [issues that are resolved, outdated, or duplicated]
```

### Optionally Close or Comment

```bash
gh issue close <number> --repo $OWNER/$REPO --comment "Closing as resolved/outdated. See #<newer-issue> for updated version."
```

## Troubleshooting

### Problem: Label filters return nothing
**Symptom**: `--label` flag matches no issues.
**Fix**: Labels are case-sensitive and repo-specific. Run `gh label list --repo $OWNER/$REPO` to see available labels, then adjust the filter.

### Problem: Issues list exceeds --limit 100
**Symptom**: Repo has 100+ open issues and results are truncated.
**Fix**: Use `--limit 500` or paginate with `--jq 'length'` first to check total count.

## Related Skills

- `github:last-week` - Weekly summary including issues
- `github:prs` - PR health analysis
- `repo:issue` - Create properly formatted issues

Attribution

rossoctlrossoctl
View sourceMore from rossoctl →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

393431 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2459130 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

929660 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

805540 votes
View all in devops →