feat(skills): add check-issue to triage an issue #151

Merged

claudiomaradonna merged 3 commits from feat/check-issue into main

2026-10-20 16:31:57 +02:00

motoko commented

2026-10-20 16:23:43 +02:00

Collaborator

Why

No workflow took an issue someone else filed. review-pr covers other
people's pull requests and file-issue our own defects, so an outside
issue could only enter fix-bug or implement-feature, which commit to
a change before anyone knows whether the report holds.

What changed

A request to check, triage, or assess someone else's issue routes to
the new check-issue skill. It reads the issue as data, fetches the
main branch, checks the claim there, and searches for duplicates.
With the user's agreement, it runs a defect's reproduction only
through .agents/scripts/run-sandboxed.sh.
It writes verdict.md from the new .agents/templates/verdict.md:
confirmed, not reproduced, already fixed, works as intended,
duplicate, or needs information, with its evidence.
It posts nothing, and offers fix-bug or implement-feature for a
confirmed issue.
forge/gh.md and forge/fj.md gain the issue reads. The validator
requires the skill and template, and the workflows guide and README
describe them.

Non-goals: no comment, label, or close on the issue, and no eval case.

How to verify

bash tests/agent-config/template-skills-workflows.sh and
bash tests/agent-config/document-templates.sh pass the new "fails
when the template lacks" cases for check-issue and verdict.md;
both fail on main as "unexpectedly valid".
Ask an agent to check an issue by number. It writes
.plans/<time>-issue-<n>/verdict.md, asks before running a
reproduction, and posts nothing.
On the tip, bash tests/verify-agent-config.sh (265 passed),
bash tests/check-work-folder.sh (46), .agents/hooks/shellcheck.sh repo, prettier --check '**/*.md', scripts/verify-agent-config.sh,
and git diff --check main pass.
Not run: the behavioral evals, which the Maintenance section asks for
before merging; the forge reads and a sandboxed reproduction against a
live forge.

Considerations

Without bwrap, every reproduction is reported as not run, and the
verdict rests on reading the code.

## Why No workflow took an issue someone else filed. `review-pr` covers other people's pull requests and `file-issue` our own defects, so an outside issue could only enter `fix-bug` or `implement-feature`, which commit to a change before anyone knows whether the report holds. ## What changed - A request to check, triage, or assess someone else's issue routes to the new `check-issue` skill. It reads the issue as data, fetches the main branch, checks the claim there, and searches for duplicates. - With the user's agreement, it runs a defect's reproduction only through `.agents/scripts/run-sandboxed.sh`. - It writes `verdict.md` from the new `.agents/templates/verdict.md`: confirmed, not reproduced, already fixed, works as intended, duplicate, or needs information, with its evidence. - It posts nothing, and offers `fix-bug` or `implement-feature` for a confirmed issue. - `forge/gh.md` and `forge/fj.md` gain the issue reads. The validator requires the skill and template, and the workflows guide and README describe them. Non-goals: no comment, label, or close on the issue, and no eval case. ## How to verify - `bash tests/agent-config/template-skills-workflows.sh` and `bash tests/agent-config/document-templates.sh` pass the new "fails when the template lacks" cases for `check-issue` and `verdict.md`; both fail on `main` as "unexpectedly valid". - Ask an agent to check an issue by number. It writes `.plans/<time>-issue-<n>/verdict.md`, asks before running a reproduction, and posts nothing. - On the tip, `bash tests/verify-agent-config.sh` (265 passed), `bash tests/check-work-folder.sh` (46), `.agents/hooks/shellcheck.sh repo`, `prettier --check '**/*.md'`, `scripts/verify-agent-config.sh`, and `git diff --check main` pass. - Not run: the behavioral evals, which the Maintenance section asks for before merging; the forge reads and a sandboxed reproduction against a live forge. ## Considerations Without bwrap, every reproduction is reported as not run, and the verdict rests on reading the code.

motoko added 3 commits

2026-10-20 16:23:51 +02:00

feat(forge): read an issue for check-issue a6af5c8c68

Add the gh and fj reads check-issue needs: the issue with its
comments, gh keeping only the comments' text, and a search of issues in
every state for one reporting the same.

feat(skills): add check-issue to triage an issue 4b435c29fa

Add a workflow that checks an issue someone else filed against the
main branch's code and gives the user a verdict from a new template,
verdict.md. A defect's reproduction runs only in the sandbox, nothing
is posted to the forge, and a confirmed issue gets an offer of fix-bug
or implement-feature. The validator now requires the skill and the
template in template state.

docs(workflows): chart check-issue e8f7219386

Add check-issue's page, its row among the entry points, and the verdict
among the documents the actions hand each other.

claudiomaradonna merged commit e8f7219386 into main

2026-10-20 16:31:57 +02:00

claudiomaradonna deleted branch feat/check-issue

2026-10-20 16:32:02 +02:00

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

claudiomaradonna/agent-foundry!151

No description provided.

Rows
Columns