Use runtime CLI signals for audits#2
Open
henrikakselsen wants to merge 1 commit into
Open
Conversation
Update Night Shift task docs to use Axe CLI and Semgrep as primary best-effort signals with heuristic fallback, expand performance guidance for Lighthouse CLI benchmarking, and document required local tools. Also align baseline tests with the current manifest and skill path so the suite passes before shipping these workflow updates. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced May 6, 2026
perandre
pushed a commit
that referenced
this pull request
May 28, 2026
* docs: Lighthouse CI on a Next.js + Vercel project Genericized writeup for setting up Lighthouse CI on a Next.js app on Vercel, paired with the merkur-frontend pilot (PR #94). Captures the five common gotchas (preview-build race, runner variance, PWA score drag, single-URL coverage, auth/draft pages) and the pilot-week "warn first, tighten later" approach. Lands in docs/ next to roadmap.md so it's discoverable from the contributor side. Closing section frames it as complementary to Henrik's PR #2 (run-Lighthouse-from-task), not in competition: the .lighthouserc.cjs page list is the same list improve-performance would target if pointed at the repo. Requested by Per Andre via #night-shift Slack thread. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: broaden scope from Next.js to all Vercel-deployed frameworks The trigger (deployment_status) and the LHCI config are platform-level, not framework-level. Title + intro were narrower than the actual content. Same workflow applies to Astro, Remix, Nuxt, plain static, etc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs: update title and intro to match broader scope Forgot to stage the content edit in the rename commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
improve-performanceto require Lighthouse CLI benchmarking on production key pages (mobile + desktop, 3 runs, median reporting, best-effort partial results)improve-accessibilityto consume Axe CLI findings as primary signal with heuristic fallback, and report signal source in PR verificationfind-security-issuesto consume Semgrep findings as primary signal with heuristic fallback, and report detection sourceTest plan
pyteston cleanmainafter baseline test fixpytestagain on feature branch with all changes appliedMade with Cursor