菜单
Review the diff between the current branch and its merge base against main (or master). Flag bugs, regressions, missing tests, and style deviations. Use when the user asks to review the current branch or a pending change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
File a GitHub issue against the harnext repo (QualityUnit/harnext) from within harnext, enriched with non-sensitive environment context. Uses a fallback chain (authenticated gh → GitHub REST API with a token → zero-auth prefilled issue URL) so reporting works even without gh installed or authenticated. Reserved for the /report-harnext-issue command.
Drive a real Chromium-based browser (Chrome/Edge/Brave) to reproduce a reported UI bug (triage mode) or verify an implementation (tester mode). Produces a video, a Playwright trace, and text artifacts (console/network/page errors, accessibility snapshots) that the agent can read to decide pass/fail. Use when the user asks to verify a UI change, reproduce a UI bug, or produce browser evidence for a PR/issue.
Detect the repo's tech stack (including monorepo sub-apps) and scaffold a project-local `setup` skill at `<cwd>/.harnext/skills/setup/` that lets future harnext sessions install dependencies, run each runnable app in the background, and attach to their logs. Use when bootstrapping a new repo.
| name | review |
| description | Review the diff between the current branch and its merge base against main (or master). Flag bugs, regressions, missing tests, and style deviations. Use when the user asks to review the current branch or a pending change. |
Review the pending changes on the current branch.
bash: git rev-parse --abbrev-ref HEAD; detect base branch (prefer main, fall back to master).bash: git merge-base HEAD <base>, then git diff <merge-base>...HEAD --stat and git diff <merge-base>...HEAD.read each changed file at HEAD — diff alone misses surrounding context.file:line citations.main isn't a shared ancestor, stop and report that instead of guessing.