Imported from ilstar/github-panel (AGENTS.md). Install upstream with npx skills add ilstar/github-panel. Copyright stays with the author.

Repository Instructions

By default, whenever starting work on a new change or feature, use a new branch and create a pull request.
Create regular (ready for review) pull requests, not draft pull requests. This overrides any user-level instruction to open drafts.
After making changes, you may always commit and push them to the working branch without asking first.
When creating a pull request, use .github/pull_request_template.md as the PR body template and fill out every section.
Every time there are code changes:
- Add or update the relevant test code as part of the change.
- Run mise run test before building the app.
- Rebuild and open the app for the user with mise run build-and-open after tests pass.
Command-line tasks live in mise.toml and mise-tasks/. The Makefile only forwards make <task> to mise run <task>; do not add logic there.

# 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 github-panel 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.

github-panel

About

Repository Instructions

Use it

Install github-panel and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews