hangar-validate
Skill1 starsChanged 3 months agoMITView on GitHub
Validate a Hangar UI or server change before merging — runs typecheck, lint, starts the real dev server, opens the browser, and outputs a focused visual checklist based on what changed. Use before merging any design, UI, or server change.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aiwf-syncSkill
- config-fieldSkill
- docs-updateSkill
- releaseSkill
- smokeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 71
After the user confirms the visual check, report:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate the current branch. Does not modify any files or commit anything.
Steps
1. Identify what changed
git diff main --stat
git diff main --name-onlySave the list of changed files — used in Step 4 to generate the visual checklist.
2. Run typecheck + lint
npm run typecheck
npm run lint -- --max-warnings=2If typecheck fails, stop here. Report the errors and tell the user to fix them — a broken build is not worth inspecting.
Report ✅/❌ for each check.
3. Start the dev server and open the app
npm run devThen open the browser:
open http://localhost:5180This starts the real Hangar instance (with the user's actual Jira boards and config). The user will inspect the UI themselves.
Tell the user: "Server is running at http://localhost:5180 — check the items in the visual checklist below, then tell me when you're done."
Wait for the user to confirm they've finished inspecting before continuing.
4. Generate visual checklist
Based on the changed files from Step 1, output only the relevant rows:
| Changed file | What to verify |
web/src/styles.css | Accent color (buttons, active states, run tags, links) in both themes; borders; spacing |
web/src/components/Board.tsx | Card rendering; run-state left borders (active/awaiting/done); column headers; drag |
web/src/components/Settings.tsx | Settings panel layout; permission toggle and any warning banner |
web/src/components/RunPanel.tsx | Run overlay; SSE output area; cost/branch sub-bar |
web/src/components/SessionsView.tsx | Session rows; run-state badges; any new action buttons |
web/src/components/AiWorkflow.tsx | aiwf board; card columns; worktree/checkout UI |
web/src/components/AiwfDocsModal.tsx | Docs browser modal; tab layout |
server/src/index.ts | No visual check — typecheck + /smoke sufficient |
server/src/config.ts | No visual check — typecheck sufficient |
server/src/aiwf.ts | No visual check — typecheck sufficient |
server/src/store.ts | No visual check — typecheck sufficient |
server/src/sessions.ts | No visual check — run a session manually to verify behavior |
To check both themes: open Settings → toggle the theme switch, or press the theme button in the topbar.
5. Report summary
After the user confirms the visual check, report:
## Validation Report — <branch name>
**Changed files:** <list from Step 1>
### Checks
- Typecheck: ✅ / ❌ <error summary>
- Lint: ✅ / ❌ <warning/error count>
### Visual Checklist
<rows from Step 4 relevant to changed files, with ✅/❌ based on user feedback>
### Result
✅ Checks pass — ready to merge
❌ Fix failures before mergingDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

