This repository was archived by the owner on Apr 14, 2026. It is now read-only.
Merged
Conversation
Adds a QA-focused skill that analyzes branch changes to systematically find edge cases, error states, and untested user flow paths in UI code. Includes a comprehensive checklist reference covering empty states, error handling, async behavior, boundary conditions, input variations, navigation, permissions, and accessibility.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9290a631cb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The skill asked users to choose between committed and uncommitted changes but then only used main...HEAD commands. Add explicit commands for staged and unstaged diffs so the analysis matches the user's selection.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Category: improvement
User Impact: AI agents can now systematically find edge cases, error states, and untested user flow paths when working on UI features.
Problem: When building UI features, the happy path gets built first but edge cases (empty states, error handling, async race conditions, boundary overflow, accessibility gaps) are easy to miss before shipping.
Solution: Adds an
edge-case-finderskill that guides agents through a structured QA analysis of branch changes — mapping the happy path, then systematically checking eight categories of edge cases, presenting findings by severity, and fixing them one at a time with user approval.Changes
File changes
.agents/skills/edge-case-finder/SKILL.md
The main skill file — defines the six-step flow: understand changes, map happy path, find edge cases across eight categories, present findings by severity, prioritize with user, and verify fixes.
.agents/skills/edge-case-finder/references/edge-case-categories.md
Exhaustive checklist reference covering empty/missing states, error/failure states, loading/async, boundary/overflow, user input variations, navigation/state, permissions/access control, and responsive/accessibility.
.claude/skills/edge-case-finder
Symlink to
../../.agents/skills/edge-case-finderfor Claude Code discovery..codex/skills/edge-case-finder
Symlink to
../../.agents/skills/edge-case-finderfor Codex discovery..cursor/skills/edge-case-finder
Symlink to
../../.agents/skills/edge-case-finderfor Cursor discovery.Reproduction Steps