intexuraos

Generate professional documentation for IntexuraOS services (apps, workers, packages). Produces 5 doc files per service, 3 per package, plus aggregated site content and cross-validation reports. Supports interactive, autonomous, and team-of-agents modes. Use when documenting services, generating docs, updating documentation, or validating doc consistency.

Orchestrate a 6-phase release workflow with automated service documentation, high-level docs updates, README "What's New" section, website improvements, and semantic versioning. Use when preparing a new release.

Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry.

Prepare an IntexuraOS release by collecting release data, triaging changes, updating docs, versions, changelog, website release highlights, and GitHub release notes.

Use when the user says "commit push", "commit and push", "push a PR", or asks Codex to finalize IntexuraOS changes by committing, pushing, and opening a pull request against development.

Use when user pastes a dev.intexuraos.cloud or intexuraos.cloud code-task URL and asks to debug, investigate, or understand what went wrong. Also use when user mentions a code task ID (task_*) with investigation intent.

Autonomous PR comment triage - fixes review feedback until CI passes

Linear issue management with automatic workflow orchestration. Handles issue creation, state transitions, and automatic splitting of large plans into tiered child issues. Use when creating issues, tracking tasks, working on INT-XXX issues, or managing Linear workflow.

Investigate IntexuraOS code-task executions when the user shares a `dev.intexuraos.cloud` or `intexuraos.cloud` code-task URL, or provides a `task_*` ID and asks to debug, investigate, or understand what happened.

Publish HTML/markdown content to intexuraos.cloud/share/claude/. Supports rich HTML (via /frontend-design), styled markdown (GitHub-flavored), and raw markdown. Use when the user asks to share, publish, or make content available as a web page.

Use when the user asks to share, publish, or make HTML or markdown content available at a public URL.

Request an automated code review from OpenAI Codex CLI. Runs codex review against a base branch and summarizes findings.

Multi-agent convergence loop for rewriting service features.md. Spawns Opus writer + 6 critic agents, iterates until quality threshold met. Use when rewriting features docs or running the convergence review loop.

This skill should be used when the user asks to "triage tech debt", "process the tech debt backlog", "consolidate technical debt", "create tech debt issues", "analyze tech debt docs", "turn tech debt into Linear issues", or mentions reviewing technical-debt.md files across the monorepo. Scans all technical-debt.md files, consolidates cross-service issues, and creates a parent Linear issue with subtasks for each approved finding. NOT for updating tech debt docs or analyzing actual source code.