Menu
Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
SolidJS framework development skill for building reactive web applications with fine-grained reactivity. Use when working with SolidJS projects including: (1) Creating components with signals, stores, and effects, (2) Implementing reactive state management, (3) Using control flow components (Show, For, Switch/Match), (4) Setting up routing with Solid Router, (5) Building full-stack apps with SolidStart, (6) Data fetching with createResource, (7) Context API for shared state, (8) SSR/SSG configuration. Triggers: solid, solidjs, solid-js, solid start, solidstart, createSignal, createStore, createEffect.
Interact with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.
Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.
Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.
Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.
Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.
| name | push-everything |
| description | Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes. |
If on main, checkout a new branch first. Stage ALL changes in the repository (not just session changes) with git add -A. Commit the changes with an appropriate message summarizing all the work. Use gh cli to see if a PR exists already. If it doesn't, create one with an appropriate title and description. If a PR does exist, query the current title and description, and update it if appropriate. Then push the changes.
