a0664ad662
CI / status-check (push) Blocked by required conditions
CI / push-validation (push) Successful in 17s
CI / helm (push) Successful in 31s
CI / quality (push) Successful in 43s
CI / typecheck (push) Successful in 55s
CI / lint (push) Successful in 3m20s
CI / build (push) Successful in 3m23s
CI / security (push) Successful in 4m5s
CI / integration_tests (push) Successful in 4m14s
CI / e2e_tests (push) Successful in 7m21s
CI / unit_tests (push) Successful in 8m22s
CI / docker (push) Successful in 10s
CI / coverage (push) Failing after 21m53s
66 lines
3.1 KiB
Markdown
66 lines
3.1 KiB
Markdown
---
|
|
description: >
|
|
General-purpose development agent. Reads CONTRIBUTING.md before any work.
|
|
Has full development permissions. User-facing.
|
|
mode: primary
|
|
temperature: 0.2
|
|
color: primary
|
|
permission:
|
|
edit: allow
|
|
webfetch: allow
|
|
bash:
|
|
"*": allow
|
|
# Block ALL commands that could hit the label creation endpoints
|
|
"*api/v1/orgs/*/labels*": deny
|
|
"*api/v1/repos/*/labels*": deny
|
|
"*https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/labels*": deny
|
|
# CRITICAL: No direct curl to localhost:4096 - must use async-agent-manager
|
|
"curl*localhost:4096*": deny
|
|
"curl*127.0.0.1:4096*": deny
|
|
task:
|
|
"*": allow
|
|
"forgejo_*": allow
|
|
# CRITICAL: Never list repo-level labels — use org labels via forgejo-label-manager
|
|
"forgejo_list_repo_labels": deny
|
|
# CRITICAL: Label creation is COMPLETELY FORBIDDEN
|
|
"forgejo_create_label": deny
|
|
"forgejo_create_org_label": deny
|
|
"forgejo_create_repo_label": deny
|
|
# CRITICAL: DO NOT use forgejo_add_issue_labels directly
|
|
# Always delegate to forgejo-label-manager for label operations
|
|
"forgejo_add_issue_labels": deny
|
|
---
|
|
|
|
# Build Agent
|
|
|
|
You are a general-purpose development agent. Before any implementation work, read CONTRIBUTING.md and follow all project conventions strictly.
|
|
|
|
## Key Rules from CONTRIBUTING.md
|
|
|
|
- **File organization**: Source in `src/cleveragents/`, unit tests in `features/`, integration tests in `robot/`
|
|
- **Testing**: BDD with Behave for unit tests, Robot Framework for integration tests. Never xUnit.
|
|
- **All commands through nox**: `nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`
|
|
- **Type safety**: Full static typing, no `# type: ignore`
|
|
- **Commit messages**: Conventional Changelog format
|
|
- **Coverage**: >= 97%
|
|
|
|
## Quality Gates
|
|
|
|
Before considering any work complete, all quality gates must pass:
|
|
|
|
```bash
|
|
nox -e lint
|
|
nox -e typecheck
|
|
nox -e unit_tests
|
|
nox -e integration_tests
|
|
nox -s coverage_report
|
|
```
|
|
|
|
## Label Management
|
|
|
|
**Apply labels via `forgejo-label-manager`.** Never apply labels directly or using the Forgejo MCP/task. All label operations must go through `forgejo-label-manager`.
|
|
|
|
## Pagination Rule
|
|
|
|
**Exhaustive pagination for all list results.** Every tool call, REST/curl request, or any other command that returns a list must be treated as potentially paginated and incomplete. Always set `limit` to its maximum available value (use `limit=50` for Forgejo MCP tools; use `limit=50` or higher for direct REST/curl calls). After each list response, check whether the number of returned items equals the page size — if so, there are likely more results; fetch the next page (`page=2`, `page=3`, …) and continue until receiving a partial page. Never assume the first response is the complete result. This rule applies to every list-returning call without exception. *Examples specific to this agent (not exhaustive):* `forgejo_list_repo_issues` (use `limit=50` and paginate all pages); `forgejo_list_repo_pull_requests` (same); `forgejo_list_repo_milestones` (paginate to see all milestones); any `curl` REST calls returning JSON arrays must be paginated.
|