verify-meterbar
Skill12 starsChanged 6 days agoMITView on GitHub
Verify MeterBar quota, cache, cost, routing, UI, and CLI changes with source invariants, offline contracts, and native app checks.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-providerSkill
- macos-menubar-appSkill
- xcode-swift-devSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run from the repository root on the configured execution host.
- Distinctive: line 16
Start with the checks that enforce the affected invariants:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Verify MeterBar
Run from the repository root on the configured execution host. Read .agents/memory/conventions.md and the issue's acceptance criteria first.
Establish the toolchain
Use full Xcode for XCTest and app/widget builds. Record xcodebuild -version and the selected developer directory. CI's release toolchain is defined in .github/actions/select-xcode/action.yml; local results on another version do not replace that CI evidence. If full Xcode or native UI access is unavailable, report that portion as unverified and complete the checks that are available. Do not substitute an XCTest shim.
Choose the evidence
Start with the checks that enforce the affected invariants:
python3 scripts/test-agent-invariants.py
scripts/check-agent-invariants.sh
swiftlint lint --strictThen read only the relevant feature guide:
| Change | Guide |
| Provider payload, quota, cache, card, widget, or hover | Quota and native UI |
| Token accumulation, cost scan, persisted totals | Cost |
| CLI output, workload routing, packaging | CLI and routing |
| Public-profile state, publishing, deletion | Public profile |
For shared model or refresh-owner changes, run the full swift test suite and build the app/widget through Xcode. For a bounded change, use the affected tests identified in the guide; expand only for an unresolved concern or a new failure. Documentation-only edits need valid references and runnable instructions, not an unrelated full rebuild.
Record the result
Keep the head SHA, actual commands, pass/fail counts, skipped checks and reasons, and the observed UI/CLI outcome in the PR. Distinguish synthetic fixtures, real account checks, local builds, and signed release artifacts. Required CI must pass on the current head before merge. Build success alone does not prove native interaction, signing, notarization, production profile deletion, or a published release.
Does 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.