Name: pre-push-preview
Author: zesun33

Instruction file imported from zesun33/zesun33.github.io (.cursor/rules/pre-push-preview.mdc). Copyright stays with the author.

Personal Website Workflow

When working in personal-website (zesun33.github.io):

Before commit

Run npm run format:check (fix with npm run format if needed).
Do not bypass Husky / Prettier hooks.

Before asking to push

Run npm run format:check (and npm run pre-push-check).
Launch the site locally and smoke-check news/publications/pages that changed.
Ask the user explicitly before any git push.

Local preview on this Windows machine

Ruby/bundle are often not on PATH. Prefer Docker via:

powershell -NoProfile -ExecutionPolicy Bypass -File _scripts/docker-serve.ps1

Or npm run preview:docker.

Requires Docker Desktop and junction C:\zesun-site → repo (script/docs explain setup).
Preview: http://127.0.0.1:4000/
Uses _scripts/preview_overrides.yml to exclude assets/jupyter/ (no jupyter CLI in the image).

Details: DEVELOPMENT.md, .workspace-rules.md.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install pre-push-preview and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zesun33-zesun33-github-io-pre-push-preview-rule", "kind": "skill", "name": "pre-push-preview", "description": "Personal website pre-commit/pre-push — Prettier + local Jekyll preview", "publisher": "zesun33", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Personal website pre-commit/pre-push — Prettier + local Jekyll preview" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/zesun33/zesun33.github.io", "path": ".cursor/rules/pre-push-preview.mdc", "ref": "c96f766757d7f18ba7138b904641ec872cff6962", "url": "https://github.com/zesun33/zesun33.github.io/blob/c96f766757d7f18ba7138b904641ec872cff6962/.cursor/rules/pre-push-preview.mdc", "key": "zesun33/zesun33.github.io/.cursor/rules/pre-push-preview.mdc" } }, "instructions": "# Personal Website Workflow\r\n\r\nWhen working in `personal-website` (zesun33.github.io):\r\n\r\n## Before commit\r\n- Run `npm run format:check` (fix with `npm run format` if needed).\r\n- Do not bypass Husky / Prettier hooks.\r\n\r\n## Before asking to push\r\n1. Run `npm run format:check` (and `npm run pre-push-check`).\r\n2. Launch the site locally and smoke-check news/publications/pages that changed.\r\n3. Ask the user explicitly before any `git push`.\r\n\r\n## Local preview on this Windows machine\r\nRuby/`bundle` are often not on PATH. Prefer Docker via:\r\n\r\n```powershell\r\npowershell -NoProfile -ExecutionPolicy B", "cost": { "context_tokens": 239 } }

pre-push-preview

About

Personal Website Workflow

Before commit

Before asking to push

Local preview on this Windows machine

Use it

Install pre-push-preview and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews