All authors
Claude Skills by NissanOhana
github.com/NissanOhana10 skills0 installs1 views
- Orangu ApplyApply exactly one reviewed proposal (status proposed, session or repo scope) to the current repository, run its own checks, and record a receipt. Use only when the user explicitly runs $orangu-apply with a suggestion id. Global proposals are review-only. Not for drafting or revising a proposal: $orangu-improve.Votes: 0GitHub stars: 2
- Orangu FeedbackSend candid beta feedback about Orangu itself through a private localhost form with an exact user-reviewed GitHub preview. Use when the user wants to report a bug, confusion, missing behavior, rough experience, or praise about Orangu. Also use when the user accepts an end-of-work feedback offer. Not for anything about a session: the `orangu analyze` command.Votes: 0GitHub stars: 2
- Orangu ImproveTurn one finding into one bounded, reviewable proposal with evidence, expected effect, risk and a verification check. Use when the user runs $orangu-improve or pastes a suggestion id from a report. Also use when the user asks what to change so the next run or session goes better, or wants an applied change verified against later sessions. Never edits the target repository. Not for applying a proposal: $orangu-apply. Not for a repo or global harness review: the `orangu harness` command.Votes: 0GitHub stars: 2
- GradersNo description providedVotes: 0GitHub stars: 2
- AnalyzeExplain what happened in one session, finished or still running, from local deterministic evidence. Use when the user asks to review a run or trace what the agent did and why it ended there. Use it to diagnose an error or retry, see where time or tokens went, or open a visual report. Use it to open the report for the session running right now. Use it to keep a report refreshed while a session runs. Not for a change proposal (/orangu:improve) or a repo or global harness review (/orangu:harness).Votes: 0GitHub stars: 2
- ApplyApply exactly one reviewed proposal (status proposed, session or repo scope) to the current repository, run its own checks, and record a receipt. Use only when the user explicitly runs /orangu:apply with a suggestion id. Global proposals are review-only. Not for drafting or revising a proposal: /orangu:improve.Votes: 0GitHub stars: 2
- FeedbackSend candid beta feedback about Orangu itself through a private localhost form with an exact user-reviewed GitHub preview. Use when the user wants to report a bug, confusion, missing behavior, rough experience, or praise about Orangu. Also use when the user accepts an end-of-work feedback offer. Not for anything about a session: /orangu:analyze.Votes: 0GitHub stars: 2
- HarnessReview what your harness declares against what your sessions used, across one repository or every session on the machine. Propose ranked changes to instruction files, hooks, skills, agents, MCP servers, plugins, and workflow config, then apply the repo items you approve by id. Use when the user asks why the same problem keeps recurring or what to change in their setup. Also use when the user wants a repo or global harness review. Not for one session: /orangu:analyze. Not for one finding: /ora...Votes: 0GitHub stars: 2
- ImproveTurn one finding into one bounded, reviewable proposal with evidence, expected effect, risk and a verification check. Use when the user runs /orangu:improve or pastes a suggestion id from a report. Also use when the user asks what to change so the next run or session goes better, or wants an applied change verified against later sessions. Never edits the target repository. Not for applying a proposal: /orangu:apply. Not for a repo or global harness review: /orangu:harness.Votes: 0GitHub stars: 2
- Show MeTurn the evidence of one session, one repository or all sessions into a slide deck and a written report, as offline HTML files. Use when the user asks for slides, a deck or a report to present or share with a team. Not for a diagnosis in chat: /orangu:analyze. Not for a change proposal: /orangu:improve.Votes: 0GitHub stars: 2