Results for “batch-requests”

Call APIs, load data into components, and handle the async lifecycle in Blazor.

Write, debug, and maintain Windows batch files (.bat/.cmd) for system administration, automation, and CLI tool development.

Apply operations across multiple files simultaneously. Pattern-based bulk modifications, search-and-replace across codebases, consistent changes to many files at once.

Applies the same change across multiple repositories in parallel using git worktrees, tests, and pull requests.

Chains Salesforce Batch Apex jobs via finish() callbacks, Flex Queue guards, or a Queueable coordinator, with guidance on state passing and test limitations.

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.

Design, review, and debug Batch Apex contracts, scope sizing, stateful behavior, chaining, and AsyncApexJob monitoring.

Batch Signal Isolation with Recipe-Driven Processing

Provides Quarkus 3.x architecture patterns for cloud-native, event-driven services with Apache Camel, including REST API design, CDI services, data access with Panache, and async processing.

Runs a relentless interview that asks every frontier question at once, round by round. Use when the user wants to be grilled on a design or map a design tree.

Selects and reviews Queueable, Batch, Future, and Schedulable Apex for callouts, large data processing, retries, and background work, with decision guidance and validation checklists.

Drafts a Petition for Writ of Certiorari to the U.S. Supreme Court under Rules 10, 13, 14, and 33. Enforces Rule 10 criteria (circuit splits, precedent conflicts, important federal questions), jurisdictional verification under 28 U.S.C. §§ 1254/1257, timeliness, document structure, and booklet formatting. Use when seeking discretionary Supreme Court review, filing a cert petition, or drafting a writ of certiorari.

The choice is not about scale or sophistication.

Consume APIs from the frontend with TanStack Query, fetch, or SWR, including caching, refetching, optimistic updates, and error handling.

Domain-Driven Design patterns. Bounded contexts, aggregates, entities, value objects, domain events, repositories, and application services. Strategic and tactical DDD for complex business domains. USE WHEN: user mentions "DDD", "Domain-Driven Design", "bounded context", "aggregate", "value object", "domain event", "ubiquitous language", "aggregate root", "domain service" DO NOT USE FOR: database schema design - use database skills; CQRS/Event Sourcing specifics - use `event-sourcing-cqrs`

Provide the shared fan-out engine used by provider-specific Jira and GitHub batch presets to enqueue child workflows with inherited runtime and stable evidence.

Creates a pull request from completed phase work, generates a rich PR body from planning artifacts, optionally runs code review, and prepares for merge.

Provides Quarkus 3.x architecture patterns for building cloud-native, event-driven services with Apache Camel, covering REST APIs, CDI services, data access with Panache, async processing, and logging.

Use when working with a stack of GitHub pull requests — creating branches, keeping the stack in sync, or merging in order. Covers Git Town setup, PR targeting, rebasing, and landing the stack.

Creates a pull request from the current feature branch with a structured summary, test results, and change description.

Archive multiple completed changes at once. Use when archiving several parallel changes.