Visual-diff verification loop for UI work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- ai-infra-agents
Research direction
Start by reading the repository’s agent-skill and verification entry points; the issue does not name specific files or tests. Define how changed screens are rendered and compared with reference screenshots, then decide how the threshold and remaining differences affect completion claims. Done means the verification step blocks unsupported completion claims and reports any differences that remain.
Written by the indexing model from the issue text.
Description
Problem (field report): agents repeatedly miss UI styling even when given explicit screenshots, and still report the work as done.
Goal: a UI-task verification step. Render the changed screen, diff it against the reference screenshot or design, and block any "done" claim until the diff is under a threshold or the remaining differences are listed.
Measure: how often UI work is reworked after handback.
Status: 📋 queued
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 561
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from protocol/perun
-
Review pipeline-tooling changes under the copy the pipeline actually runs, not the PR's own copyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
protocol/perun#1779 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Paraxial.trace returns NaN for an object at infinity when the entrance pupil is at the first surfaceOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement ios launcher
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Substrait consumer doesn't recognise `shift_left` / `shift_right` from functions_arithmetic.yamlOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/datafusion#27059 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
loteran/Arctis-Sound-Manager#368 ·
Maintainers usually reply within 1 day
-
feed submission
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MobilityData/mobility-database-catalogs#1787 ·
Maintainers usually reply within 2 days