All authors
Claude Skills by HigorAlves
github.com/HigorAlves84 skills0 installs0 views
- Adr WritingAuthor and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in docs/adr/NNNN-*.md. Use to lock in an architectural decision or to supersede an ADR.Votes: 0GitHub stars: 6
- Agent BrowserBrowser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test web/Electron apps.Votes: 0GitHub stars: 6
- Architecture PatternsImplement Clean, Hexagonal (Ports & Adapters), and Domain-Driven architecture patterns. Use when designing service layers, refactoring monoliths into bounded contexts, or fixing layer dependency cycles.Votes: 0GitHub stars: 6
- Browser QaThe canonical browser-QA protocol for web changes — target resolution, env attach, the driver gate (Playwright primary, agent-browser, Claude-in-Chrome), validator dispatch, chrome evidence packet. Use when running browser QA; /orc:qa and /orc:flow Phase 6 delegate here.Votes: 0GitHub stars: 6
- CalloutsThe orc callout palette — emoji-header blockquotes in conversation, GitHub-flavored [!TYPE] form for GitHub-bound output. Use when about to add an insight, caution, gate, preview, or danger block to the conversation or to a PR/doc.Votes: 0GitHub stars: 6
- Caveman PrUltra-compressed, signal-only pull request descriptions. Use when opening a PR or when the user says "write a PR description", "PR body", "draft the PR", or invokes /caveman-pr.Votes: 0GitHub stars: 6
- Caveman ReviewUltra-compressed code review comments — one line per finding: location, problem, fix. Use when the user says \"review this PR\", \"code review\", \"review the diff\", \"/review\", or invokes /caveman-review.Votes: 0GitHub stars: 6
- Ci RoutingThe canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the single-render rule, and the fix-then-re-watch loop. Use after orc-ci-investigator returns; /orc:ci Phase 3 and /orc:flow's post-open CI gate delegate here.Votes: 0GitHub stars: 6
- Code DiscoveryUse when discovering or navigating a codebase before planning, implementing, debugging, or refactoring — prefer a Graphify code-graph query over broad Glob/Grep/Read to cut token cost, with automatic fallback to grep when Graphify is absent, stale, or unhealthy.Votes: 0GitHub stars: 6
- Codebase DesignShared vocabulary for designing deep modules — seam, adapter, depth, leverage, locality. Use when designing or reshaping a module's interface, deciding where a seam goes, making code more testable or AI-navigable, or when another orc skill or agent needs the deep-module vocabulary.Votes: 0GitHub stars: 6
- Dependency ManagementAudit, survey, and upgrade project dependencies safely — majors escalated, never auto-applied. Use when auditing dependencies for vulnerabilities, checking outdated packages, bumping a dependency, or when /orc:deps is invoked.Votes: 0GitHub stars: 6
- Dispatching Parallel AgentsDispatch parallel subagents with focused, self-contained briefs — each gets exactly the context it needs, never your session history. Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.Votes: 0GitHub stars: 6
- Doc WritingShared scaffolding for numbered design/spec docs — outline, NNNN-* numbering, review gates, doc-type map (PRD/TRD/RFC/ADR/postmortem). Referenced by orc:prd/trd/rfc/adr-writing + postmortem.Votes: 0GitHub stars: 6
- Docker Best PracticesDocker expert — image optimization, security hardening, multi-stage builds, orchestration, production deployment. Use when writing or reviewing Dockerfiles, Compose, or container deploys.Votes: 0GitHub stars: 6
- Documentation WritingDiátaxis documentation expert. Use when writing high-quality software documentation guided by the Diátaxis framework — tutorials, how-tos, reference, and explanation.Votes: 0GitHub stars: 6
- Domain ModelingMaintain a project's ubiquitous language and decision record against CONTEXT.md. Use when defining or disputing domain terminology, when a design session resolves a term that belongs in CONTEXT.md, or when a decision made mid-session passes the ADR gate.Votes: 0GitHub stars: 6
- Env ProvisioningProvision a fast, reproducible dev environment for QA or standalone use — healthcheck-gated boot, reuse/teardown rules, host-mode fallback. Protocol for /orc:env, /orc:qa Phase 4, /orc:flow Phase 6, and the orc-env-provisioner agent.Votes: 0GitHub stars: 6
- Error Handling PatternsError handling patterns across languages — exceptions, Result types, propagation, graceful degradation. Use when implementing error handling, designing APIs, or improving reliability.Votes: 0GitHub stars: 6
- Evidence PublishDeliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.Votes: 0GitHub stars: 6
- Executing PlansExecute a written implementation plan batch-by-batch — load it, review critically, implement task by task, and stop for review between batches. Use when you have a written implementation plan to execute in a separate session with review checkpoints.Votes: 0GitHub stars: 6
- ExplainerBuild the narrated what-was-made walkthrough for a QA packet: script from plan + acceptance, demo pass, segments.json, animate graphics, kokoro narration, orc-explain assemble. Use from /orc:explain and the flow explainer gate. Not for QA itself.Votes: 0GitHub stars: 6
- Finishing A Development BranchGuide the completion of a development branch by presenting structured options for merge, PR, or cleanup. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.Votes: 0GitHub stars: 6
- Flow PhasesPer-phase playbooks for /orc:flow Phases 2–9, loaded one at a time as the flow reaches each phase. Use only from /orc:flow — Read the single references/PHASE-N-*.md for the phase being entered, never all of them.Votes: 0GitHub stars: 6
- GatesThe canonical AskUserQuestion conventions for every orc gate — class-tagged header chips, Recommended-first options, side-by-side `preview` for preview-then-confirm, multiSelect chunking, notes as the rewrite channel, and the --auto ladder. Use when about to render an orc gate.Votes: 0GitHub stars: 6
- Gh CliGitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API. Use for any gh command or GitHub operation from the terminal.Votes: 0GitHub stars: 6
- Git Advanced WorkflowsAdvanced Git workflows - rebase, cherry-pick, bisect, worktrees, reflog - for clean history and recovery. Use when managing complex histories, collaborating on branches, or troubleshooting a repo.Votes: 0GitHub stars: 6
- Git CommitExecute git commit with conventional-commit analysis, intelligent staging, and message generation from the diff. Use when the user asks to commit changes, create a git commit, or mentions /commit.Votes: 0GitHub stars: 6
- Grill MeA relentless decision-by-decision interview to sharpen a plan or design until reaching shared understanding.Votes: 0GitHub stars: 6
- Grill With DocsGrill a plan or design while writing the docs as you go — the interview plus a live glossary (CONTEXT.md) and ADRs captured the moment decisions land.Votes: 0GitHub stars: 6
- GrillingRound-based interview engine under orc's grill entry points (orc:grill-me, /orc:plan --grill, /orc:rfc --grill, /orc:flow medium+ scope). Use when stress-testing a plan or design decision-by-decision, or when a session must end with nothing left silently assumed.Votes: 0GitHub stars: 6
- HandoffCompact the current conversation into a redacted handoff document, saved to the OS temp dir, that a fresh agent in another session or tool can pick up — /orc:resume is the counterpart for resuming in-repo orc state.Votes: 0GitHub stars: 6
- Improve Codebase ArchitectureFind architecture-deepening opportunities in a codebase. Use when the user wants to improve architecture, find refactors, consolidate coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 6
- Inline ReviewPost a real GitHub PR review with line-anchored inline comments; invoked by /orc:code-review after findings. For commenting on your OWN diff, prefer the bundled /code-review --comment.Votes: 0GitHub stars: 6
- Jira CliAtlassian CLI (acli) reference for Jira work items — create, sub-task, link, view, JQL search, transition. Use to file/move/link a Jira ticket from the terminal or when /orc:jira is invoked.Votes: 0GitHub stars: 6
- Jira HierarchyThe Jira backlog contract — Epic-as-micro-PRD, Stories, concurrency-sliced Tasks, and the mandatory child-ticket template. Use when creating or restructuring Jira epics, stories, or task breakdowns, or when enforcing ticket structure — /orc:jira-breakdown and orc-jira-architect are built on it.Votes: 0GitHub stars: 6
- MapAsk which orc command, skill, or flow fits your situation — the router over everything orc ships.Votes: 0GitHub stars: 6
- Mobile Ios DesigniOS Human Interface Guidelines and SwiftUI patterns for native apps. Use when designing iOS interfaces, building SwiftUI views, or aligning apps with Apple's design principles.Votes: 0GitHub stars: 6
- Nestjs Best PracticesNestJS best practices and architecture patterns for production apps. Use when writing, reviewing, or refactoring NestJS code — modules, dependency injection, security, and performance.Votes: 0GitHub stars: 6
- Next Best PracticesNext.js best practices. Use when writing, reviewing, or refactoring Next.js code — App Router routing, RSC/server-client boundaries, data fetching, route handlers, metadata, image/font optimization.Votes: 0GitHub stars: 6
- Nodejs Best PracticesNode.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.Votes: 0GitHub stars: 6
- Playwright QaDriver P of orc:browser-qa — browser QA with Playwright Test and the stock planner/generator/healer agents against a resolved QA target; yields a stitched step-tagged video, traces, and qa-manifest.json. Use when browser-qa selects the playwright driver; falls back to agent-browser.Votes: 0GitHub stars: 6
- Postgresql OptimizationWrite or review PostgreSQL-specific SQL: JSONB, arrays, custom/range/geometric types, indexing, full-text search, window functions, extensions, and RLS. Use for PG-unique features and code review.Votes: 0GitHub stars: 6
- Postgresql Table DesignDesign or review a PostgreSQL-specific schema: data types, indexing, constraints, partitioning, RLS, performance patterns, and advanced features. Use when modeling or auditing PG tables.Votes: 0GitHub stars: 6
- Postmortem WritingAuthor blameless incident postmortems — timeline, root cause(s), contributing factors, action items. Use after a production incident (outage, data loss, security event, regression) or a near-miss.Votes: 0GitHub stars: 6
- Pr Size BudgetUse when opening a PR or planning slices — defines the soft 300 LOC budget, the exclusion list, the shared gate prompt for ship/flow/stack-pr, and the override syntax.Votes: 0GitHub stars: 6
- Prd WritingAuthor Product Requirements Documents (PRDs) from scratch — interview-driven, templated, published to docs/prds/NNNN-*.md. Use for "write a PRD for X", an unsettled new feature, or /orc:prd.Votes: 0GitHub stars: 6
- PrototypeThrowaway code that answers a design question before real implementation — slots between /orc:plan and /orc:start. Use when feeling out whether logic, a state machine, or a data shape holds up, or when comparing radically different UI variants on one route before committing to a design.Votes: 0GitHub stars: 6
- Qa TargetsResolve WHERE browser QA runs — named targets in .orc/targets.json (local, staging, preview), the Target gate, credential references (literal | op:// | env:), guard rule. Use before env provisioning in /orc:qa, /orc:flow Phase 6, /orc:evidence.Votes: 0GitHub stars: 6
- Readme WritingCreate a comprehensive, well-structured README.md for the current project by reviewing the entire codebase first. Use when the user asks to create, write, improve, or regenerate a project README.Votes: 0GitHub stars: 6
- Receiving Code ReviewEvaluate code review feedback with technical rigor and verification — never performative agreement or blind implementation. Use when receiving code review feedback, before implementing suggestions.Votes: 0GitHub stars: 6