nicolasakf

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.

Reviews inventory age, sell-through, stale stock, and stockout risk for retail or ecommerce operations teams.

Analyzes revenue, cost, gross profit, and margin by product, category, channel, store, customer, or period for retail and operations teams.

Inspects the working tree, groups changes into atomic commits, stages explicit paths, generates conventional commit messages (succinct or detailed), and commits. In a populated chat, prefer staging only session-related files. Use when the user wants to commit, asks to commit, or needs a commit message.

Bumps package semver, commits release changes with conventional commits, tags the release, and publishes to npm. Use when cutting a release, running npm publish, bumping package.json version, or shipping a new npm package version.

Resolves Git merge conflicts safely by inspecting markers, choosing or combining changes, validating the result, and completing merge, rebase, or cherry-pick. Use when git reports conflicts, conflict markers appear in files, or the user asks to fix merge/rebase conflicts.

Explains how to use Unity to keep Agent Skills synchronized across coding agents.

Builds and reviews reproducible strategy backtests in notebooks. Use when creating a new backtest, adapting an existing strategy analysis, validating portfolio exposures, benchmarking returns, or summarizing performance and drawdown results.