Skip to content

chore(local-issues): add severity categories, summary output, broaden triggers #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
philoserf merged 1 commit into from
Mar 24, 2026
Merged

chore(local-issues): add severity categories, summary output, broaden triggers #335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 30 additions & 2 deletions skills/local-issues/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,25 @@
---
argument-hint: "[path or scope]"
allowed-tools: Read, Grep, Glob, Bash, Write
description: Reviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, or reviewing a project for issues. Creates issue files in `.issues/` directory.
description: Reviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, doing a code review, finding problems, or reviewing a project for issues. Creates issue files in `.issues/` directory.
---

Review this codebase for bugs, design issues, and code cleanliness problems. Be specific and cite file paths and line numbers.

Scope the review to `$ARGUMENTS` if provided, otherwise review the entire project.
Scope the review to `$ARGUMENTS` if provided, otherwise review the entire project. Examples: `src/auth/`, `lib/api.ts`, `security`, `tests/`.

## What to look for

Prioritize by severity:

| Severity | Category |
| ------------ | --------------------------------------------------------- |
| **Critical** | Security vulnerabilities, data loss, crashes |
| **High** | Correctness bugs, missing error handling, race conditions |
| **Medium** | Design issues, code smells, missing validation |
| **Low** | Style inconsistencies, naming, minor cleanup |

## Process

For each issue found:

Expand All @@ -19,6 +32,7 @@ Each issue file should follow this format:
```text
# Title

**Severity:** critical | high | medium | low
**Location:** `file:line`

## Description
Expand All @@ -29,3 +43,17 @@ What's wrong and why it matters.

Concrete recommendation.
```

## Summary

After creating all issue files, output a summary:

```text
| # | Severity | File:Line | Issue |
|---|----------|-----------|-------|
| 1 | high | src/a.ts:42 | Missing null check |
| 2 | medium | lib/b.py:17 | Bare except clause |

Total: {N} issues ({critical} critical, {high} high, {medium} medium, {low} low)
Files created in .issues/
```
Loading