Top Skills for Developers

---
name: code-review
description: >
  Reviews code, diffs, and files for bugs, security vulnerabilities, style
  issues, and improvement opportunities. Triggers when asked to review code,
  check a file, audit a function, or look for issues in the codebase.
allowed-tools: Read(*) Bash(git diff *)
---

You are an expert code reviewer. Analyse the provided code or diff and
produce a structured report.

## Output format

**Summary**: One sentence describing what the code does.

**Issues found**:
| Severity | File / Line | Issue | Suggestion |
|----------|-------------|-------|------------|

Severity levels: High  Medium  Low

**Overall assessment**: Approve / Request changes — with one-line rationale.

Focus on: correctness, security (OWASP Top 10), performance, readability.
Skip nitpicks unless they cause real problems.

---
name: commit
description: >
  Stages all changes and writes a descriptive commit message following
  Conventional Commits format. Use when asked to commit, save changes,
  or push work to the repository.
allowed-tools: Bash(git add *) Bash(git diff --staged) Bash(git commit *) Bash(git push *)
---

Stage all changes with `git add -A`, inspect the diff, then write a commit message.

Format: <type>(<scope>): <summary>

Types: feat · fix · chore · docs · refactor · test · style

- Summary: imperative mood, under 72 characters, no full stop
- Body (optional): explain *why*, not what — wrap at 72 chars

After committing, push to origin: git push origin HEAD

Print the final commit hash and summary line when done.

---
name: pr-description
description: >
  Generates a clear pull request title and description from the current
  branch diff. Use when asked to write a PR, describe changes for review,
  or prepare a pull request description.
allowed-tools: Bash(git diff main...) Bash(git log main... --oneline) Bash(git branch --show-current)
---

Write a pull request description for this branch.

1. Run `git branch --show-current` to get the branch name.
2. Run `git log main... --oneline` to list commits.
3. Run `git diff main...` to see all changes.

## Output

**Title**: One line, imperative mood, under 72 characters.

**Description**:

### What
Short paragraph describing what changed and why.

### How
Bullet list of the key implementation decisions.

### Testing
How this was tested (unit tests, manual steps, etc.).

### Notes
Any caveats, follow-up tasks, or reviewer guidance.

Keep the tone professional and concise.