odylith-github-release-closeout
openbooklet.com/s/odylith-github-release-closeoutopenbooklet.com/s/odylith-github-release-closeout@1.0.0GET /api/v1/skills/odylith-github-release-closeoutUse this maintainer-only skill when the operator needs to prepare or apply public GitHub issue updates for issues fixed in a release.
Use this skill only when the user explicitly invokes `$odylith-atlas-render` or asks to render Atlas from the Mermaid catalog.
Use this skill only when the user explicitly invokes `$odylith-compass-refresh` or asks to refresh Compass and wait for the current pass to settle.
Use this skill only when the user explicitly invokes `$odylith-registry-validate` or asks to validate Registry component inventory contracts.
Refresh Atlas diagrams from change-watch metadata.
Create grounded Radar backlog workstreams.
Validate Radar backlog and plan linkage contracts.
Use when an Odylith Casebook bug create or update needs prerequisite checks.
Enforce the anti-slop contract when duplicate helpers, fake modularization, or oversized-file pressure show up.
Use when a bounded execution note needs to be appended into Compass.
Update or inspect the Odylith component registry and component dossier truth.
Use when a known Odylith anchor needs the smallest useful local context packet.
Work with Odylith context-engine packets, retrieval, and routing support flows.
Update Atlas diagram catalog truth and related source diagrams for Odylith.
Use when Odylith Discipline pressure behavior, host/lane parity, or credit-safe benchmark proof needs validation.
Verify or repair the current Odylith install.
Auto-indexed from odylith/odylith
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.