All authors
Claude Skills by HigorAlves
github.com/HigorAlves84 skills0 installs0 views
- Release ManagementCut a semver release from conventional commits — bump, grouped changelog, annotated tag, GitHub release. Use when releasing, tagging a version, bumping semver, or writing release notes.Votes: 0GitHub stars: 6
- Requesting Code ReviewDispatch a code-reviewer subagent with precisely crafted context to catch issues in finished work before they cascade. Use when completing tasks, implementing major features, or before merging to verify work meets requirements.Votes: 0GitHub stars: 6
- ResearchDelegate a research question to a background agent that reads primary sources and lands cited findings as a Markdown file in the repo. Use when the user asks to research a topic, when docs or API facts need verifying at the source, or when reading legwork should run in the background.Votes: 0GitHub stars: 6
- Resolving Merge ConflictsResolve an in-progress git merge or rebase conflict by tracing each side's intent back to primary sources before touching a hunk; always resolve, never --abort. Use when a merge or rebase stops on conflicts, or when conflict markers appear anywhere in the working tree.Votes: 0GitHub stars: 6
- Review ContractThe canonical review findings contract — JSON schema, severity enum, mechanical severity→event mapping, confidence ≥0.8 rule. Use when producing, merging, or posting structured review findings, or when building a new reviewer agent.Votes: 0GitHub stars: 6
- Rfc WritingAuthor RFCs — design docs that propose a non-trivial change before implementation, surface alternatives, and invite critique, in docs/rfcs/NNNN-*.md. Use for "write an RFC" or a multi-team feature.Votes: 0GitHub stars: 6
- Sentry CliGuide for using the Sentry CLI from the command line. Use when viewing issues, events, projects, traces, dashboards, releases, making API calls, or authenticating with Sentry via CLI.Votes: 0GitHub stars: 6
- ShadcnAdd, search, fix, debug, style, and compose shadcn/ui components. Applies to shadcn/ui, component registries, --preset codes, or any project with a components.json. Triggers on "shadcn init".Votes: 0GitHub stars: 6
- Skill WritingCreate new agent skills following orc's house conventions and CI gates. Use when creating, writing, or building a skill for THIS plugin. For skill evals, trigger-rate measurement, and description tuning, use the official skill-creator plugin.Votes: 0GitHub stars: 6
- Stack PrUse when breaking a too-big branch into a stack of smaller chained PRs — commit-based default, --smart agent-reshape, gh-stack detection, cross-links. Invoked by /orc:stack-pr and /orc:ship's size gate.Votes: 0GitHub stars: 6
- State ProtocolThe canonical .orc/ state contract — orc.json session schema, checkpoint frontmatter + resume-digest shape, the orc-state CLI, read-for-data vs route-from-state, and the resumed-session startup sequence. Use when registering, checkpointing, reading, or resuming .orc/ session state.Votes: 0GitHub stars: 6
- Stripe Best PracticesGuide Stripe integration decisions — API choice, Connect, billing, Treasury, key/webhook security. Use when building, modifying, or reviewing any Stripe payment, marketplace, or subscription.Votes: 0GitHub stars: 6
- Swiftui Best PracticesComprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.Votes: 0GitHub stars: 6
- Systematic DebuggingRoot-cause-first debugging discipline — build a red-capable feedback loop, minimise the repro, rank falsifiable hypotheses, fix at the source. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.Votes: 0GitHub stars: 6
- Tailwind Design SystemBuild scalable Tailwind CSS v4 design systems — design tokens, component libraries, responsive patterns. Use for component libraries, design systems, or standardizing UI patterns.Votes: 0GitHub stars: 6
- TddTest-driven development with the red-green-refactor loop. Use when building features or fixing bugs via TDD, requesting integration tests, or asking for test-first development.Votes: 0GitHub stars: 6
- To IssuesBreak a plan, spec, or PRD into independently-grabbable tracker issues using tracer-bullet vertical slices. Use when converting a plan into issues or implementation tickets.Votes: 0GitHub stars: 6
- To PrdTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.Votes: 0GitHub stars: 6
- To QuestionnaireTurn a decision you can't answer alone into a questionnaire for someone else to fill in — grill the send, not the subject. Joins the to-* family alongside orc:to-issues and orc:to-prd.Votes: 0GitHub stars: 6
- Tracker ConfigThe shared read-protocol and missing-config gate for the repo's tracker layer (docs/agents/issue-tracker.md, triage-labels.md, domain.md). Use when a command needs the configured tracker, its labels, or the Jira-enabled answer — /orc:setup writes the files; this skill reads them.Votes: 0GitHub stars: 6
- Trd WritingAuthor Technical Requirements Documents (TRDs) — turn a settled PRD into interfaces, data shapes, failure modes, and constraints in docs/trds/NNNN-*.md. Use for "write a TRD" or /orc:trd.Votes: 0GitHub stars: 6
- TurborepoTurborepo monorepo build-system guidance — turbo.json task pipelines, caching, the turbo CLI, --filter/--affected, CI, env vars, and packages. Use when configuring tasks, sharing code between apps, or debugging the cache.Votes: 0GitHub stars: 6
- Typescript Advanced TypesMaster TypeScript's advanced type system - generics, conditional, mapped, template-literal, utility types, inference, and type guards. Use for complex type logic, reusable type utilities, or compile-time type safety.Votes: 0GitHub stars: 6
- Using Git WorktreesCreate isolated git worktrees with smart directory selection and safety checks. Use when starting feature work that needs isolation, or before executing an implementation plan.Votes: 0GitHub stars: 6
- Using Orcorc's iron rules, instruction priority, and skill-routing discipline. Injected at every SessionStart; required reading before your first action.Votes: 0GitHub stars: 6
- Vercel Composition PatternsReact composition patterns that scale (compound components, render props, context, React 19 APIs). Use when refactoring boolean-prop proliferation, building component libraries, or designing reusable APIs.Votes: 0GitHub stars: 6
- Vercel React Best PracticesReact and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js components, data fetching, or bundles for performance.Votes: 0GitHub stars: 6
- Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before committing or opening PRs — evidence before assertions. Doctrine skill (preloaded into orc-implementer), not a command — the bundled /verify covers interactive one-off behavioral checks.Votes: 0GitHub stars: 6
- VitestVitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.Votes: 0GitHub stars: 6
- Wait WhatStop and re-pitch — the last message did not land; say it again simply, in the project's own vocabulary.Votes: 0GitHub stars: 6
- WizardGenerate an interactive bash wizard walking a human through work only they can perform — credentials, secrets, one-off migrations. Use when provisioning infrastructure or third-party credentials, or when orc-env-provisioner escalates a human-only condition; never for steps the agent can do itself.Votes: 0GitHub stars: 6
- Workspace ModeUse when cwd is a parent dir holding multiple sibling git repos — defines repo auto-detection, --repos/--repo/--all-repos/--this-repo precedence, per-repo dispatch, and linked-PR mechanics.Votes: 0GitHub stars: 6
- Writing For Agentsorc's doctrine layer for writing any document an agent consumes — skills, AGENTS.md/CLAUDE.md, reference docs. Use when writing or editing a SKILL.md or AGENTS.md/CLAUDE.md, tuning a skill description that fires unreliably, or deciding what to inline versus push behind a pointer.Votes: 0GitHub stars: 6
- Writing PlansWrite a comprehensive implementation plan of bite-sized TDD tasks that an engineer with zero codebase context could execute — exact files, code, tests, and verification steps. Use when you have a spec or requirements for a multi-step task, before touching code.Votes: 0GitHub stars: 6