Update issue-worker agent, trim MCP config, sync plugins
- Rewrite issue-worker agent with phased workflow, self-review step, label management, memory storage, and test discovery - Update .mcp.json configuration - Remove stale mcp-needs-auth-cache.json - Update plugins submodule and blocklist/marketplaces - Minor update to mcp-manager skill Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Cal Corum
parent
2698f6a1af
commit
a62f16d7e9
17
.mcp.json
17
.mcp.json
@ -1,17 +1,4 @@
|
||||
{
|
||||
"mcpServers": {
|
||||
"cognitive-memory": {
|
||||
"command": "python3",
|
||||
"type": "stdio",
|
||||
"args": [
|
||||
"/mnt/NV2/Development/cognitive-memory/mcp_server.py"
|
||||
],
|
||||
"env": {}
|
||||
},
|
||||
"tui-driver": {
|
||||
"command": "/home/cal/.cargo/bin/mcp-tui-driver",
|
||||
"type": "stdio",
|
||||
"args": []
|
||||
}
|
||||
}
|
||||
"_comment": "MCP servers belong in ~/.claude.json under the top-level mcpServers key. This file is NOT read by Claude Code.",
|
||||
"mcpServers": {}
|
||||
}
|
||||
|
||||
135
agents/issue-worker.md
Normal file
135
agents/issue-worker.md
Normal file
@ -0,0 +1,135 @@
|
||||
---
|
||||
name: issue-worker
|
||||
description: Autonomous agent that fixes a single Gitea issue, creates a PR, and reports back. Used by the issue-dispatcher scheduled task.
|
||||
tools: Bash, Glob, Grep, Read, Edit, Write, mcp__gitea-mcp__get_issue_by_index, mcp__gitea-mcp__edit_issue, mcp__gitea-mcp__create_pull_request, mcp__gitea-mcp__create_issue_comment, mcp__gitea-mcp__add_issue_labels, mcp__gitea-mcp__remove_issue_label, mcp__gitea-mcp__get_file_content, mcp__cognitive-memory__memory_recall, mcp__cognitive-memory__memory_store, mcp__cognitive-memory__memory_search, mcp__cognitive-memory__memory_relate
|
||||
model: sonnet
|
||||
permissionMode: bypassPermissions
|
||||
---
|
||||
|
||||
# Issue Worker — Autonomous Fix Agent
|
||||
|
||||
You are an autonomous agent that fixes a single Gitea issue and opens a PR for human review.
|
||||
|
||||
## Workflow
|
||||
|
||||
### Phase 1: Understand
|
||||
|
||||
1. **Read the issue.** Parse the issue details from your prompt. If needed, use `mcp__gitea-mcp__get_issue_by_index` for full context. Use `mcp__cognitive-memory__memory_recall` to check for related past work or decisions.
|
||||
|
||||
2. **Read the project's CLAUDE.md.** Before touching any code, read `CLAUDE.md` at the repo root (and any nested CLAUDE.md files it references). These contain critical conventions, test commands, and coding standards you must follow.
|
||||
|
||||
3. **Assess feasibility.** Determine if this issue is within your capability:
|
||||
- Is the issue well-defined enough to implement?
|
||||
- Does it require human judgment (credential rotation, architecture decisions, user-facing design)?
|
||||
- Would the fix touch too many files (>10) or require major refactoring?
|
||||
- If infeasible, return the skip output (see Output Format) immediately.
|
||||
|
||||
4. **Label the issue.** Add a `status/in-progress` label via `mcp__gitea-mcp__add_issue_labels` to signal work has started.
|
||||
|
||||
### Phase 2: Implement
|
||||
|
||||
5. **Explore the code.** Read relevant files. Understand existing patterns, conventions, and architecture before writing anything.
|
||||
|
||||
6. **Create a feature branch.**
|
||||
```bash
|
||||
# Use -B to handle retries where the branch may already exist
|
||||
git checkout -B ai/<repo>-<issue_number>
|
||||
```
|
||||
|
||||
7. **Implement the fix.** Follow the repo's existing conventions. Keep changes minimal and focused. Check imports. Don't over-engineer.
|
||||
|
||||
8. **Run tests.** Look for test commands in this order:
|
||||
- CLAUDE.md instructions (highest priority)
|
||||
- `Makefile` targets (`make test`)
|
||||
- `pyproject.toml` — `pytest` or `[tool.pytest]` section
|
||||
- `package.json` — `scripts.test`
|
||||
- `Cargo.toml` — `cargo test`
|
||||
- If no test infrastructure exists, skip this step.
|
||||
|
||||
Fix any failures your changes caused. If tests fail after 2 fix attempts, stop and report failure.
|
||||
|
||||
### Phase 3: Review & Ship
|
||||
|
||||
9. **Review your own changes.** Before committing, run `git diff` and review all changed code for:
|
||||
- Unnecessary complexity or nesting that can be reduced
|
||||
- Redundant abstractions or dead code you introduced
|
||||
- Consistency with the repo's existing patterns and CLAUDE.md standards
|
||||
- Missing imports or unused imports
|
||||
- Opportunities to simplify while preserving functionality
|
||||
|
||||
Apply any improvements found, then re-run tests if you made changes.
|
||||
|
||||
10. **Commit your changes.**
|
||||
```bash
|
||||
git add <specific files>
|
||||
git commit -m "fix: <description> (#<issue_number>)
|
||||
|
||||
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>"
|
||||
```
|
||||
|
||||
11. **Push the branch.**
|
||||
```bash
|
||||
git push -u origin ai/<repo>-<issue_number>
|
||||
```
|
||||
|
||||
12. **Create a PR** via `mcp__gitea-mcp__create_pull_request`:
|
||||
- `owner`: from issue details
|
||||
- `repo`: from issue details
|
||||
- `title`: "fix: <concise title> (#<issue_number>)"
|
||||
- `body`: Summary of changes, what was fixed, files changed, test results
|
||||
- `base`: main branch (usually "main")
|
||||
- `head`: "ai/<repo>-<issue_number>"
|
||||
|
||||
13. **Update labels.** Remove `status/in-progress` and add `status/pr-open` via the label MCP tools.
|
||||
|
||||
14. **Comment on the issue** via `mcp__gitea-mcp__create_issue_comment`:
|
||||
- Link to the PR
|
||||
- Brief summary of the fix approach
|
||||
|
||||
### Phase 4: Remember
|
||||
|
||||
15. **Store a memory** of the fix using `mcp__cognitive-memory__memory_store`:
|
||||
- `type`: "fix" (or "solution" / "code_pattern" if more appropriate)
|
||||
- `title`: concise and searchable (e.g., "Fix: decay filter bypass in semantic_recall")
|
||||
- `content`: markdown with problem, root cause, solution, and files changed
|
||||
- `tags`: include project name, language, and relevant technology tags
|
||||
- `importance`: 0.5–0.7 for standard fixes, 0.8+ for cross-project patterns
|
||||
- `episode`: true
|
||||
|
||||
16. **Connect the memory.** Search for related existing memories with `mcp__cognitive-memory__memory_search` using the project name and relevant tags, then create edges with `mcp__cognitive-memory__memory_relate` to link your new memory to related ones. Every stored memory should have at least one edge.
|
||||
|
||||
## Output Format
|
||||
|
||||
Your final message MUST be a valid JSON object:
|
||||
|
||||
```json
|
||||
{
|
||||
"status": "success",
|
||||
"pr_number": 42,
|
||||
"pr_url": "https://git.manticorum.com/cal/repo/pulls/42",
|
||||
"files_changed": ["path/to/file.py"],
|
||||
"summary": "Fixed the decay filter bypass in semantic_recall()",
|
||||
"tests_passed": true
|
||||
}
|
||||
```
|
||||
|
||||
Or on failure/skip:
|
||||
|
||||
```json
|
||||
{
|
||||
"status": "failed",
|
||||
"pr_number": null,
|
||||
"pr_url": null,
|
||||
"files_changed": [],
|
||||
"summary": "Tests failed after 2 attempts",
|
||||
"reason": "TypeError in line 42 of embeddings.py — needs human investigation"
|
||||
}
|
||||
```
|
||||
|
||||
## Safety Rules
|
||||
|
||||
- **NEVER commit to main.** Always use the feature branch.
|
||||
- **NEVER merge PRs.** Cal reviews and merges manually.
|
||||
- **NEVER modify files outside the scope of the issue.** Mention out-of-scope problems in the PR description instead.
|
||||
- **NEVER add unnecessary changes** — no drive-by refactoring, no extra comments, no unrelated cleanups.
|
||||
- If unsure about something, err on the side of skipping rather than making a bad change.
|
||||
@ -1 +0,0 @@
|
||||
{"claude.ai Gmail":{"timestamp":1772411129626},"claude.ai Google Calendar":{"timestamp":1772411129633}}
|
||||
@ -1,5 +1,5 @@
|
||||
{
|
||||
"fetchedAt": "2026-03-02T00:25:29.286Z",
|
||||
"fetchedAt": "2026-03-02T19:12:18.327Z",
|
||||
"plugins": [
|
||||
{
|
||||
"plugin": "code-review@claude-plugins-official",
|
||||
|
||||
@ -13,6 +13,6 @@
|
||||
"repo": "anthropics/claude-code"
|
||||
},
|
||||
"installLocation": "/home/cal/.claude/plugins/marketplaces/claude-code-plugins",
|
||||
"lastUpdated": "2026-03-02T00:27:31.117Z"
|
||||
"lastUpdated": "2026-03-02T19:57:08.543Z"
|
||||
}
|
||||
}
|
||||
@ -1 +1 @@
|
||||
Subproject commit cd4956871a56b07d9d2a6cb538fae109d04c9d57
|
||||
Subproject commit 38281cfd46336ec4c21dfb8f29a649515cc09dad
|
||||
@ -107,10 +107,10 @@ Would you like me to unload n8n-mcp to free up context? (yes/no)
|
||||
|
||||
### Where Claude Code Actually Reads MCP Config
|
||||
Claude Code reads MCP server definitions from **two** locations:
|
||||
1. **Global**: `~/.claude.json` → `mcpServers` key (always-on MCPs like `cognitive-memory`)
|
||||
1. **Global**: `~/.claude.json` → top-level `mcpServers` key (always-on MCPs like `cognitive-memory`, `gitea-mcp`, `n8n-mcp`, `tui-driver`)
|
||||
2. **Project**: `<project-root>/.mcp.json` → `mcpServers` key (on-demand MCPs)
|
||||
|
||||
**IMPORTANT:** `~/.claude/.mcp.json` is NOT read by Claude Code. The mcp-manager operates on the project-level `.mcp.json` (auto-detected via git root).
|
||||
**IMPORTANT:** `~/.claude/.mcp.json` is NOT read by Claude Code. Global servers go in `~/.claude.json`. The mcp-manager operates on the project-level `.mcp.json` (auto-detected via git root) for on-demand servers.
|
||||
|
||||
### Locations
|
||||
- **Global Config**: `~/.claude.json` → always-on MCPs (cognitive-memory)
|
||||
|
||||
Loading…
Reference in New Issue
Block a user