Skip to content

feat(eval): two-agent file-edit tracker eval (#64) #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
codevibesmatter wants to merge 6 commits into
base: main
Choose a base branch
from
Open

feat(eval): two-agent file-edit tracker eval (#64) #65

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
eb3f853
plan: two-agent file-edit tracker eval (#64)
Apr 17, 2026
f87140f
feat(eval): harness supports agents[] for concurrent scenarios (#64)
Apr 17, 2026
3e03080
feat(eval): two-commits + scoped-commit assertions (#64)
Apr 17, 2026
6bd08ba
feat(eval): two-agent-tracker scenario wiring (#64)
Apr 17, 2026
7d92f13
fix(eval): address review issues on #64 P1 implementation
Apr 17, 2026
7885bcd
feat(skills): create gh issue in kata-close research branch
Apr 19, 2026
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
22 changes: 21 additions & 1 deletion batteries/skills/kata-close/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,27 @@ gh issue comment {issue_number} --body "{comment_body}"

Commit and push only. Tests are not required for research mode — skip step 2.

No PR creation, no issue update.
No PR creation.

Create a GitHub issue to capture the research findings and any follow-up work:

```bash
gh issue create \
--title "{research_title}" \
--body "## Summary
{research_summary}

## Findings
{key_findings}

## Follow-up
{followup_items}

Research doc: {research_doc_path}" \
--label research
```

Use the research document's title and top-level summary for `{research_title}` and `{research_summary}`. Link the created issue number back in the commit message or as a follow-up comment if needed.

### If in planning mode

Expand Down
Loading
Loading