Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion self-development/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ Picks up open GitHub issues labeled `needs-actor` and performs automated triage.
| **Concurrency** | 8 |

**For each issue, the agent:**
1. Classifies with exactly one `kind/*` label (`kind/bug`, `kind/feature`, `kind/api`, `kind/docs`)
1. Classifies with exactly one `kind/*` label (`kind/bug`, `kind/feature`, `kind/cleanup`, `kind/docs`)
2. Checks if the issue has already been fixed by a merged PR or recent commit
3. Checks if the issue references outdated APIs, flags, or features
4. Detects duplicate issues
Expand Down
11 changes: 9 additions & 2 deletions self-development/agentconfig.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,22 @@ spec:

## Standards
- Do not create duplicate issues — check existing issues first with `gh issue list`
- Keep changes minimal and focused
- Keep changes minimal and focused. Do not refactor, reorganize, or 'improve' code beyond what was explicitly requested
- For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML

## Project Conventions
- Use Makefile targets instead of discovering build/test commands yourself:
- `make verify` — run all verification checks (lint, fmt, vet, etc.)
- `make update` — update all generated files
- `make test` — run all unit tests
- `make test-integration` — run integration tests
- e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead
- `make build` — build binary
- Always try to add or improve tests when modifying code
- Always try to add or improve tests (including integration, e2e) when modifying code
- Logging conventions: start log messages with capital letters and do not end with punctuation
- Commit messages: do not include PR links in commit messages

## Directory Structure
- `cmd/` — CLI entrypoints
- `test/e2e/` — end-to-end tests
- `.github/workflows/` — CI workflows
11 changes: 9 additions & 2 deletions self-development/kelos-fake-strategist.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,25 @@ spec:

## Standards
- Do not create duplicate issues — check existing issues first with `gh issue list`
- Keep changes minimal and focused
- Keep changes minimal and focused. Do not refactor, reorganize, or 'improve' code beyond what was explicitly requested
- For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML

## Project Conventions
- Use Makefile targets instead of discovering build/test commands yourself:
- `make verify` — run all verification checks (lint, fmt, vet, etc.)
- `make update` — update all generated files
- `make test` — run all unit tests
- `make test-integration` — run integration tests
- e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead
- `make build` — build binary
- Always try to add or improve tests when modifying code
- Always try to add or improve tests (including integration, e2e) when modifying code
- Logging conventions: start log messages with capital letters and do not end with punctuation
- Commit messages: do not include PR links in commit messages

## Directory Structure
- `cmd/` — CLI entrypoints
- `test/e2e/` — end-to-end tests
- `.github/workflows/` — CI workflows
---
apiVersion: kelos.dev/v1alpha1
kind: TaskSpawner
Expand Down
11 changes: 9 additions & 2 deletions self-development/kelos-fake-user.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,25 @@ spec:

## Standards
- Do not create duplicate issues — check existing issues first with `gh issue list`
- Keep changes minimal and focused
- Keep changes minimal and focused. Do not refactor, reorganize, or 'improve' code beyond what was explicitly requested
- For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML

## Project Conventions
- Use Makefile targets instead of discovering build/test commands yourself:
- `make verify` — run all verification checks (lint, fmt, vet, etc.)
- `make update` — update all generated files
- `make test` — run all unit tests
- `make test-integration` — run integration tests
- e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead
- `make build` — build binary
- Always try to add or improve tests when modifying code
- Always try to add or improve tests (including integration, e2e) when modifying code
- Logging conventions: start log messages with capital letters and do not end with punctuation
- Commit messages: do not include PR links in commit messages

## Directory Structure
- `cmd/` — CLI entrypoints
- `test/e2e/` — end-to-end tests
- `.github/workflows/` — CI workflows
---
apiVersion: kelos.dev/v1alpha1
kind: TaskSpawner
Expand Down
11 changes: 9 additions & 2 deletions self-development/kelos-self-update.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,25 @@ spec:

## Standards
- Do not create duplicate issues — check existing issues first with `gh issue list`
- Keep changes minimal and focused
- Keep changes minimal and focused. Do not refactor, reorganize, or 'improve' code beyond what was explicitly requested
- For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML

## Project Conventions
- Use Makefile targets instead of discovering build/test commands yourself:
- `make verify` — run all verification checks (lint, fmt, vet, etc.)
- `make update` — update all generated files
- `make test` — run all unit tests
- `make test-integration` — run integration tests
- e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead
- `make build` — build binary
- Always try to add or improve tests when modifying code
- Always try to add or improve tests (including integration, e2e) when modifying code
- Logging conventions: start log messages with capital letters and do not end with punctuation
- Commit messages: do not include PR links in commit messages

## Directory Structure
- `cmd/` — CLI entrypoints
- `test/e2e/` — end-to-end tests
- `.github/workflows/` — CI workflows
---
apiVersion: kelos.dev/v1alpha1
kind: TaskSpawner
Expand Down
2 changes: 1 addition & 1 deletion self-development/kelos-triage.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ spec:
Read the issue carefully and apply exactly one `kind/*` label:
- `kind/bug` — something is broken or behaving incorrectly
- `kind/feature` — a request for new functionality
- `kind/api` — related to API changes or additions
- `kind/cleanup` — refactoring, technical debt, or configuration alignment
- `kind/docs` — documentation improvement or fix

Apply the label:
Expand Down
11 changes: 9 additions & 2 deletions self-development/kelos-workers.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,25 @@ spec:

## Standards
- Do not create duplicate issues — check existing issues first with `gh issue list`
- Keep changes minimal and focused
- Keep changes minimal and focused. Do not refactor, reorganize, or 'improve' code beyond what was explicitly requested
- For CI/release workflows, always use existing Makefile targets rather than reimplementing build logic in YAML

## Project Conventions
- Use Makefile targets instead of discovering build/test commands yourself:
- `make verify` — run all verification checks (lint, fmt, vet, etc.)
- `make update` — update all generated files
- `make test` — run all unit tests
- `make test-integration` — run integration tests
- e2e tests are hard to run locally. Push changes and use the PR's CI jobs to run them instead
- `make build` — build binary
- Always try to add or improve tests when modifying code
- Always try to add or improve tests (including integration, e2e) when modifying code
- Logging conventions: start log messages with capital letters and do not end with punctuation
- Commit messages: do not include PR links in commit messages

## Directory Structure
- `cmd/` — CLI entrypoints
- `test/e2e/` — end-to-end tests
- `.github/workflows/` — CI workflows
---
apiVersion: kelos.dev/v1alpha1
kind: TaskSpawner
Expand Down
Loading