claudy 0.2.2

Modern multi-provider launcher for Claude CLI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

# Issue Tracker

Issues are tracked in GitHub at **epicsagas/claudy** using `gh` CLI.

## Prerequisites

Verify `gh` is authenticated:

```bash
gh auth status
```

If not authenticated, run `gh auth login` and follow the prompts.

## Issue Templates

Two templates are available in `.github/ISSUE_TEMPLATE/`:

- **Bug Report** (`bug_report.yml`) — Structured form for reproducible defects
- **Feature Request** (`feature_request.yml`) — Structured form for enhancements

## Auto-labeling

Issues created via templates are automatically labeled:

| Template | Auto-applied labels |
|---|---|
| Bug Report | `bug`, `needs-triage` |
| Feature Request | `enhancement`, `needs-triage` |
| Dependabot | `dependencies`, `needs-triage` |

## Creating Issues

```bash
# Bug report (interactive)
gh issue create --template bug_report.yml

# Feature request (interactive)
gh issue create --template feature_request.yml

# Quick issue with labels
gh issue create --title "fix: description" --label "bug,needs-triage"
```

## Linking Issues to PRs

Use Conventional Commits with issue references:

```
fix(channel): resolve webhook timeout on large payloads

Closes #42
```

Keywords: `Closes #N`, `Fixes #N`, `Resolves #N` — these auto-close the issue on merge.

## Security Issues

**Do NOT file security vulnerabilities as GitHub issues.** Follow the process described in `SECURITY.md` instead.

## Common Commands

```bash
# List open issues
gh issue list --state open

# View issue details
gh issue view 42

# Add a label
gh issue edit 42 --add-label "ready-for-agent"

# Close an issue
gh issue close 42 --reason "completed"
```