メニュー
Creates GitHub issues for the Orion repo following project conventions. Use when the user asks to create an issue, file a bug, add a feature request, or track work in GitHub issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-github-issues |
| description | Creates GitHub issues for the Orion repo following project conventions. Use when the user asks to create an issue, file a bug, add a feature request, or track work in GitHub issues. |
When creating issues for the Orion-app repo (https://github.com/nicolasakf/Orion-app):
gh issue create or output markdown for manual creation# [Title - same as issue title]
Status: [Backlog | Not started | In progress]
Component: [Component name - optional]
Feature: [Feature name - optional]
Child Component: [Child component - optional]
Type: [New Feature | Bug Fix | refactor]
[Description: bullets or paragraph]
---
- **Component**: [Name]
- **Child Component**: [Name - if applicable]
- **Feature**: [Name - if applicable]
Every issue has exactly 2 labels: one type label and one status label.
Type labels (pick one):
| Label | Use when |
|---|---|
bug | Something isn't working |
new-feature | New feature or request |
refactor | Code refactoring |
optimization | Performance optimization |
Status labels (pick one):
| Label | Use when |
|---|---|
backlog | Planned for future |
not-started | Work has not started |
in-progress | Work is in progress |
Examples: bug + not-started, new-feature + backlog, refactor + in-progress
gh issue create --repo nicolasakf/Orion-app --title "Title" --body "$BODY" --label "label1" --label "label2"
Or with a body file:
gh issue create --repo nicolasakf/Orion-app --title "Title" --body-file issue-body.md --label "new-feature" --label "not-started"
See examples.md for real issue bodies from the repo.
Publishes an Orion release end-to-end — version bump, build, push release prep, wait for GitHub checks/install smoke (skippable when CI already passed on the pre-bump commit), tag, GitHub release, npm/PyPI publish via scripts/publish-release.sh (NPM_TOKEN + PyPI token in ~/.zprofile), sync version tags in Orion-api and Orion-docs, then post-release verification. Use when the user asks to publish a release, ship a version, bump and publish orion-notebook or orion-ui, or cut a new npm/PyPI release.
Builds Orion-native notebook UI outputs with the Python `orion_ui` package. Auto-loaded for notebook work; use when the user asks for interactive notebook UI features like plotly charts, sliders, selects, buttons, etc.
Operates Orion user and workspace settings safely. Use when reading, creating, validating, or changing `~/.orion/settings.json` or `<workspace>/.orion/settings.json`, settings overrides, model pins, provider config, workspace-level settings, or recovering user settings from automatic backups in `~/.orion/settings-backup`.
Creates or edits Orion notebook App View selections from notebook cells and outputs. Use when the user asks to make a notebook app, dashboard, report UI, or app view from notebook content.
Reference for Orion notebook metadata contract. Use when deciding which fields under notebook `metadata.orion` or cell `metadata.orion` are supported, what values they accept, and which keys are legacy/internal-only.
Runs a plain-language business analysis of uploaded data, producing key findings, data quality notes, charts, and suggested next questions for non-technical users.