Compare commits
2 Commits
v0.2.5
...
11f86f5d99
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
11f86f5d99 | ||
|
|
f7076c9ac8 |
@@ -36,6 +36,18 @@ These rules apply to every task across every project, regardless of harness.
|
||||
4. **Goal-driven execution.** Define clear success criteria up front for every task.
|
||||
Loop — implement, verify, refine — until those criteria are met. Don't claim
|
||||
completion without evidence (tests pass, command output, observed behavior).
|
||||
5. **Trunk-Based Development — commit directly to main.** Every commit is one
|
||||
logical change (one tool, one fix, one test) with passing tests. Main is always
|
||||
deployable. Never create long-lived feature branches.
|
||||
|
||||
**Exception — parallel agents on same repo:** If another agent is known to be
|
||||
actively working on the same repo simultaneously, create a short-lived branch
|
||||
(`agent/<description>`), finish the task, and merge to main within the same
|
||||
session. Do not leave agent branches open between sessions.
|
||||
|
||||
**Exception — external contributor or client four-eyes requirement:** Use
|
||||
PR flow only when a human reviewer outside the project is required. Document
|
||||
the reason in PROJECT.md.
|
||||
|
||||
## Default stack
|
||||
|
||||
@@ -49,6 +61,7 @@ These rules apply to every task across every project, regardless of harness.
|
||||
| Search | pgvector (vector), BM25 | Qdrant (when >1M vectors or hybrid retrieval) | — |
|
||||
| Logging | slog (structured) | — | — |
|
||||
| Testing | Table-driven, testify | — | — |
|
||||
| Agents (Go) | google.golang.org/adk + pkg/litellm adapter | — | — |
|
||||
|
||||
Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
|
||||
@@ -58,9 +71,12 @@ Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
- **Errors**: `fmt.Errorf("operation: %w", err)` — never naked, never log-and-return
|
||||
- **Naming**: stdlib conventions, no stuttering
|
||||
- **Architecture**: prefer stdlib over frameworks, constructor injection, env-var config parsed into typed structs
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), one concern per PR, PR describes *why* not *what*
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), commit directly to main,
|
||||
one logical change per commit, CI is the quality gate
|
||||
- **Never**: long-lived feature branches, PRs for solo work, direct push without
|
||||
passing `task check` locally first
|
||||
- **Security**: no secrets in code, govulncheck before adding deps, SOPS for encrypted config
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc are pre-approved; anything else needs justification in the commit message
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc, google.golang.org/adk (agent projects only) are pre-approved; anything else needs justification in the commit message
|
||||
|
||||
## Infrastructure
|
||||
|
||||
@@ -208,9 +224,11 @@ Key skills:
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -248,98 +266,29 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
@@ -37,9 +37,11 @@
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -77,98 +79,29 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
@@ -41,6 +41,18 @@ These rules apply to every task across every project, regardless of harness.
|
||||
4. **Goal-driven execution.** Define clear success criteria up front for every task.
|
||||
Loop — implement, verify, refine — until those criteria are met. Don't claim
|
||||
completion without evidence (tests pass, command output, observed behavior).
|
||||
5. **Trunk-Based Development — commit directly to main.** Every commit is one
|
||||
logical change (one tool, one fix, one test) with passing tests. Main is always
|
||||
deployable. Never create long-lived feature branches.
|
||||
|
||||
**Exception — parallel agents on same repo:** If another agent is known to be
|
||||
actively working on the same repo simultaneously, create a short-lived branch
|
||||
(`agent/<description>`), finish the task, and merge to main within the same
|
||||
session. Do not leave agent branches open between sessions.
|
||||
|
||||
**Exception — external contributor or client four-eyes requirement:** Use
|
||||
PR flow only when a human reviewer outside the project is required. Document
|
||||
the reason in PROJECT.md.
|
||||
|
||||
## Default stack
|
||||
|
||||
@@ -54,6 +66,7 @@ These rules apply to every task across every project, regardless of harness.
|
||||
| Search | pgvector (vector), BM25 | Qdrant (when >1M vectors or hybrid retrieval) | — |
|
||||
| Logging | slog (structured) | — | — |
|
||||
| Testing | Table-driven, testify | — | — |
|
||||
| Agents (Go) | google.golang.org/adk + pkg/litellm adapter | — | — |
|
||||
|
||||
Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
|
||||
@@ -63,9 +76,12 @@ Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
- **Errors**: `fmt.Errorf("operation: %w", err)` — never naked, never log-and-return
|
||||
- **Naming**: stdlib conventions, no stuttering
|
||||
- **Architecture**: prefer stdlib over frameworks, constructor injection, env-var config parsed into typed structs
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), one concern per PR, PR describes *why* not *what*
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), commit directly to main,
|
||||
one logical change per commit, CI is the quality gate
|
||||
- **Never**: long-lived feature branches, PRs for solo work, direct push without
|
||||
passing `task check` locally first
|
||||
- **Security**: no secrets in code, govulncheck before adding deps, SOPS for encrypted config
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc are pre-approved; anything else needs justification in the commit message
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc, google.golang.org/adk (agent projects only) are pre-approved; anything else needs justification in the commit message
|
||||
|
||||
## Infrastructure
|
||||
|
||||
@@ -213,9 +229,11 @@ Key skills:
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -253,100 +271,31 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
---
|
||||
|
||||
131
.cursorrules
131
.cursorrules
@@ -39,6 +39,18 @@ These rules apply to every task across every project, regardless of harness.
|
||||
4. **Goal-driven execution.** Define clear success criteria up front for every task.
|
||||
Loop — implement, verify, refine — until those criteria are met. Don't claim
|
||||
completion without evidence (tests pass, command output, observed behavior).
|
||||
5. **Trunk-Based Development — commit directly to main.** Every commit is one
|
||||
logical change (one tool, one fix, one test) with passing tests. Main is always
|
||||
deployable. Never create long-lived feature branches.
|
||||
|
||||
**Exception — parallel agents on same repo:** If another agent is known to be
|
||||
actively working on the same repo simultaneously, create a short-lived branch
|
||||
(`agent/<description>`), finish the task, and merge to main within the same
|
||||
session. Do not leave agent branches open between sessions.
|
||||
|
||||
**Exception — external contributor or client four-eyes requirement:** Use
|
||||
PR flow only when a human reviewer outside the project is required. Document
|
||||
the reason in PROJECT.md.
|
||||
|
||||
## Default stack
|
||||
|
||||
@@ -52,6 +64,7 @@ These rules apply to every task across every project, regardless of harness.
|
||||
| Search | pgvector (vector), BM25 | Qdrant (when >1M vectors or hybrid retrieval) | — |
|
||||
| Logging | slog (structured) | — | — |
|
||||
| Testing | Table-driven, testify | — | — |
|
||||
| Agents (Go) | google.golang.org/adk + pkg/litellm adapter | — | — |
|
||||
|
||||
Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
|
||||
@@ -61,9 +74,12 @@ Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
- **Errors**: `fmt.Errorf("operation: %w", err)` — never naked, never log-and-return
|
||||
- **Naming**: stdlib conventions, no stuttering
|
||||
- **Architecture**: prefer stdlib over frameworks, constructor injection, env-var config parsed into typed structs
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), one concern per PR, PR describes *why* not *what*
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), commit directly to main,
|
||||
one logical change per commit, CI is the quality gate
|
||||
- **Never**: long-lived feature branches, PRs for solo work, direct push without
|
||||
passing `task check` locally first
|
||||
- **Security**: no secrets in code, govulncheck before adding deps, SOPS for encrypted config
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc are pre-approved; anything else needs justification in the commit message
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc, google.golang.org/adk (agent projects only) are pre-approved; anything else needs justification in the commit message
|
||||
|
||||
## Infrastructure
|
||||
|
||||
@@ -211,9 +227,11 @@ Key skills:
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -251,98 +269,29 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
@@ -4,8 +4,6 @@ on:
|
||||
push:
|
||||
branches: [main]
|
||||
tags: ["v*"]
|
||||
pull_request:
|
||||
branches: [main]
|
||||
|
||||
env:
|
||||
IMAGE: gitea-mcp
|
||||
@@ -43,7 +41,6 @@ jobs:
|
||||
name: Build & Import
|
||||
needs: check
|
||||
runs-on: self-hosted
|
||||
if: github.event_name != 'pull_request'
|
||||
outputs:
|
||||
image-tag: ${{ steps.meta.outputs.sha-tag }}
|
||||
steps:
|
||||
|
||||
5
.githooks/pre-push
Normal file
5
.githooks/pre-push
Normal file
@@ -0,0 +1,5 @@
|
||||
#!/usr/bin/env bash
|
||||
set -euo pipefail
|
||||
echo "→ Running task check before push..."
|
||||
task check
|
||||
echo "✓ pre-push check passed"
|
||||
131
AGENTS.md
131
AGENTS.md
@@ -36,6 +36,18 @@ These rules apply to every task across every project, regardless of harness.
|
||||
4. **Goal-driven execution.** Define clear success criteria up front for every task.
|
||||
Loop — implement, verify, refine — until those criteria are met. Don't claim
|
||||
completion without evidence (tests pass, command output, observed behavior).
|
||||
5. **Trunk-Based Development — commit directly to main.** Every commit is one
|
||||
logical change (one tool, one fix, one test) with passing tests. Main is always
|
||||
deployable. Never create long-lived feature branches.
|
||||
|
||||
**Exception — parallel agents on same repo:** If another agent is known to be
|
||||
actively working on the same repo simultaneously, create a short-lived branch
|
||||
(`agent/<description>`), finish the task, and merge to main within the same
|
||||
session. Do not leave agent branches open between sessions.
|
||||
|
||||
**Exception — external contributor or client four-eyes requirement:** Use
|
||||
PR flow only when a human reviewer outside the project is required. Document
|
||||
the reason in PROJECT.md.
|
||||
|
||||
## Default stack
|
||||
|
||||
@@ -49,6 +61,7 @@ These rules apply to every task across every project, regardless of harness.
|
||||
| Search | pgvector (vector), BM25 | Qdrant (when >1M vectors or hybrid retrieval) | — |
|
||||
| Logging | slog (structured) | — | — |
|
||||
| Testing | Table-driven, testify | — | — |
|
||||
| Agents (Go) | google.golang.org/adk + pkg/litellm adapter | — | — |
|
||||
|
||||
Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
|
||||
@@ -58,9 +71,12 @@ Exploratory: Rust, Zig — I'll tell you when I want these.
|
||||
- **Errors**: `fmt.Errorf("operation: %w", err)` — never naked, never log-and-return
|
||||
- **Naming**: stdlib conventions, no stuttering
|
||||
- **Architecture**: prefer stdlib over frameworks, constructor injection, env-var config parsed into typed structs
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), one concern per PR, PR describes *why* not *what*
|
||||
- **Git**: conventional commits (`feat:`, `fix:`, `chore:`), commit directly to main,
|
||||
one logical change per commit, CI is the quality gate
|
||||
- **Never**: long-lived feature branches, PRs for solo work, direct push without
|
||||
passing `task check` locally first
|
||||
- **Security**: no secrets in code, govulncheck before adding deps, SOPS for encrypted config
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc are pre-approved; anything else needs justification in the commit message
|
||||
- **Dependencies**: prefer stdlib. testify, slog, templ, sqlc, google.golang.org/adk (agent projects only) are pre-approved; anything else needs justification in the commit message
|
||||
|
||||
## Infrastructure
|
||||
|
||||
@@ -208,9 +224,11 @@ Key skills:
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -248,98 +266,29 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
111
CLAUDE.md
111
CLAUDE.md
@@ -37,9 +37,11 @@
|
||||
|
||||
### Git
|
||||
- Conventional commits: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`
|
||||
- Branch naming: `feat/short-description`, `fix/short-description`
|
||||
- PRs: one concern per PR, description explains *why* not *what*
|
||||
- **Branch protection:** always work on a feature branch, open a PR, never push directly to main
|
||||
- **Trunk-Based Development:** commit directly to main. One logical change per commit.
|
||||
- Run `task check` locally before every push. CI is the quality gate, not branch protection.
|
||||
- No feature branches, no PRs for solo/agent work.
|
||||
- Exception: if a parallel agent session is active on this repo, use a short-lived
|
||||
`agent/<description>` branch and merge within the same session.
|
||||
|
||||
### Security
|
||||
- No secrets in code, ever — use env vars or SOPS-encrypted files
|
||||
@@ -77,98 +79,29 @@ When acting as a coding agent on this project:
|
||||
3. If unsure about a convention, check `DECISIONS.md` or ask
|
||||
4. Never modify files outside the project root without explicit permission
|
||||
5. When adding a dependency, explain why in the commit message
|
||||
6. Always work on a feature branch and open a PR — never push directly to main
|
||||
6. Commit directly to main. Run `task check` before every push. Never create
|
||||
feature branches unless a parallel agent is simultaneously active on this repo.
|
||||
7. For client projects: never send code or context to cloud APIs — use local models via LiteLLM
|
||||
|
||||
## Current sprint — gitea-mcp v0.2 patch (2026-05-14)
|
||||
## Current state — v0.2.5 (2026-05-17)
|
||||
|
||||
### Context
|
||||
The main v0.2 batch (repo_create, repo_update, repo_mirror_push, repo_delete,
|
||||
repo_tree, repo_topics_update, file_read dir-fix, issue_get, release_create,
|
||||
create_project_from_template) was implemented and pushed directly to main.
|
||||
All v0.2 work is complete and deployed. No active sprint.
|
||||
|
||||
This sprint fixes three remaining gaps found during code review on 2026-05-14.
|
||||
These are blockers for `hyperguild new-project`.
|
||||
### What shipped
|
||||
|
||||
### Issues to fix (all three in one PR: `fix/v02-patch`)
|
||||
| Tag | PR | Tools / fixes |
|
||||
|-----|----|---------------|
|
||||
| v0.2.2 | #21 | repo_create, repo_update, repo_mirror_push |
|
||||
| v0.2.3 | #22 | repo_tree, repo_topics_update, file_read dir fix |
|
||||
| v0.2.4 | #23 | issue_get, release_create, repo_delete |
|
||||
| v0.2.5 | #26 | repo_update archived+template, create_project_from_template template_name, pr_files_diff loop fix |
|
||||
|
||||
#### #12 — repo_update: add `archived` and `template` fields
|
||||
**File:** `internal/gitea/repos.go` → `UpdateRepoArgs` struct
|
||||
**File:** `internal/tools/repo_update.go` → input schema + args struct
|
||||
Current main: `e31fd3f`. CI green. Deployed via Flux.
|
||||
|
||||
Add to `UpdateRepoArgs`:
|
||||
```go
|
||||
Archived *bool
|
||||
Template *bool
|
||||
```
|
||||
### Next up
|
||||
|
||||
Add to tool input schema:
|
||||
```json
|
||||
"archived": {
|
||||
"type": "boolean",
|
||||
"description": "Mark repo as archived (read-only). Requires confirm=<repo name>."
|
||||
},
|
||||
"template": {
|
||||
"type": "boolean",
|
||||
"description": "Toggle template repo flag."
|
||||
}
|
||||
```
|
||||
1. **`hyperguild new-project` v1** — primary next target.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for full flow spec.
|
||||
|
||||
Add confirm-guard for `archived=true` (same pattern as `private=false`):
|
||||
```go
|
||||
if args.Archived != nil && *args.Archived {
|
||||
if args.Confirm != args.Name {
|
||||
return nil, fmt.Errorf("setting archived=true is irreversible: set confirm=%q to proceed", args.Name)
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
New test cases to add in `repo_update_test.go`:
|
||||
- `TestRepoUpdateTool_Archive` — happy path with confirm
|
||||
- `TestRepoUpdateTool_ArchiveRequiresConfirm` — missing confirm returns error
|
||||
- `TestRepoUpdateTool_SetTemplate` — no confirm needed
|
||||
|
||||
#### #24 — create_project_from_template: make template selectable
|
||||
**File:** `internal/tools/create_project_from_template.go`
|
||||
|
||||
Add optional `template_name` param to input schema:
|
||||
```json
|
||||
"template_name": {
|
||||
"type": "string",
|
||||
"enum": ["template-go-web", "template-go-agent"],
|
||||
"description": "Template repo to generate from. Defaults to template-go-web.",
|
||||
"default": "template-go-web"
|
||||
}
|
||||
```
|
||||
|
||||
The tool should use `args.TemplateName` if set, fall back to the hardcoded default.
|
||||
Remove the hardcoded template name from `cmd/gitea-mcp/main.go` constructor call —
|
||||
the tool resolves it internally.
|
||||
|
||||
New test case: `TestCreateProjectFromTemplate_AgentTemplate`
|
||||
|
||||
#### #25 — pr_files_diff: fix same diff returned for all files
|
||||
**File:** `internal/tools/pr_files_diff.go`
|
||||
|
||||
There is a loop bug where all file entries in the response contain the same diff
|
||||
(the first file's diff is reused for every subsequent file). Find the loop and
|
||||
ensure each iteration reads and assigns the correct diff for its own file.
|
||||
|
||||
Reproduce: call `pr_files_diff` on any PR with 3+ files, verify each file has
|
||||
a distinct diff.
|
||||
|
||||
### Definition of done
|
||||
|
||||
- [ ] `task check` passes
|
||||
- [ ] `repo_update` accepts `archived` and `template` params
|
||||
- [ ] `archived=true` requires `confirm=<repo name>`
|
||||
- [ ] `create_project_from_template` accepts `template_name` param, defaults to `template-go-web`
|
||||
- [ ] `pr_files_diff` returns distinct diff per file
|
||||
- [ ] All new test cases pass
|
||||
- [ ] PR `fix/v02-patch` merged to main via PR (not direct push)
|
||||
|
||||
### After this sprint
|
||||
|
||||
Next: `hyperguild new-project` v1 implementation.
|
||||
See brain node `adr-new-project-gitea-first-github-mirror` for the full flow spec.
|
||||
Also: verify end-to-end mirror flow (issue #19) once `repo_mirror_push` is confirmed working.
|
||||
2. **Issue #19** — end-to-end mirror flow verification.
|
||||
`repo_mirror_push` is implemented but the full flow (create repo → add push mirror → verify sync to GitHub) has not been tested manually. Do this before relying on it in production.
|
||||
|
||||
11
README.md
11
README.md
@@ -2,3 +2,14 @@
|
||||
|
||||
Streamable HTTP MCP service exposing Gitea repo operations to Claude apps.
|
||||
See `~/dev/AI/infra/docs/superpowers/specs/2026-05-04-gitea-mcp-gitops-workflow-design.md`.
|
||||
|
||||
## Quickstart
|
||||
|
||||
```bash
|
||||
task setup:hooks # installs .githooks/pre-push — runs task check before every push
|
||||
task check # context sync + lint + test + vet
|
||||
task build # produces bin/gitea-mcp
|
||||
```
|
||||
|
||||
This repo uses Trunk-Based Development. Commit directly to `main`. The pre-push
|
||||
hook enforces the quality gate locally; CI re-runs `task check` on every push.
|
||||
|
||||
@@ -47,6 +47,13 @@ tasks:
|
||||
cmds:
|
||||
- bash scripts/context-sync.sh
|
||||
|
||||
setup:hooks:
|
||||
desc: Install git hooks (.githooks/pre-push)
|
||||
cmds:
|
||||
- git config core.hooksPath .githooks
|
||||
- chmod +x .githooks/pre-push
|
||||
- echo "✓ git hooks installed (pre-push runs task check)"
|
||||
|
||||
context:sync:claude:
|
||||
cmds: [bash scripts/context-sync.sh claude]
|
||||
context:sync:agents:
|
||||
|
||||
Reference in New Issue
Block a user