superforge-verify
SolidGate that blocks any completion claim until there is empirical runtime evidence — the test suite actually run, both mobile and desktop viewports checked, and native iOS or Android simulator runs confirmed. Use before saying a task is done, fixed, or shipped. Use when the user says "is it done", "did it work", "verify", "double check", "are you sure", "before we ship", "確認して", "検証して", "本当に動く", "終わった", "動作確認", or runs /superforge-verify.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- takaoumehara
- Repository
- takaoumehara/superforge-skill
- Created
- 3 days ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
superforge-test
Drive implementation through Red-Green-Refactor TDD across Web (Jest, Vitest, Playwright), iOS (Swift Testing, XCTest), and Android (JUnit, Compose Test), verifying each red and green state by actually running the suite. Use when the user says "write tests", "TDD", "test first", "add test coverage", "refactor safely", "テストを書いて", "テスト先に", "TDD", "リファクタリング", "テストが無い", or runs /superforge-test.
verify-done
An evidence gate that must pass before claiming any task is complete. Use this at the end of every coding task, right before saying "done", "fixed", "implemented", or "should work", and whenever tempted to assume code works without running it. Applies to features, bug fixes, refactors, config changes, and one-off scripts alike. If work is being handed back to a human, this gate comes first.
superlazy-verify
Evidence before any completion claim. Use immediately before saying done/fixed/passing, before any ✅, and before committing or creating a PR.