add-query

Scaffold CQRS queries with handler, repository method, and GET endpoint.

2|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill add-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-query
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/add-query
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill add-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a new CQRS query with a handler and GET endpoint following project conventions, reducing boilerplate and ensuring consistency.

Core Features & Use Cases

  • Generates query, response, handler, and endpoint scaffolds for both single-entity and list queries.
  • Follows SignalBeam project conventions for naming, structure, and OpenAPI metadata.
  • Speeds up backend feature delivery, enabling consistent read-model patterns across services.

Quick Start

Run the add-query skill to scaffold a new CQRS query in the target service.

Frequently Asked Questions about add-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a CQRS query with a handler and endpoint in .NET?

You can scaffold a CQRS query by generating query, response, handler, repository method, and endpoint templates together. This approach follows SignalBeam .NET conventions, reducing boilerplate for read-model patterns across microservices.

What is the best way to reduce boilerplate when adding read-model queries across microservices?

Scaffolding CQRS queries ensures consistency and reduces boilerplate by generating handlers, repository methods, and GET endpoints according to project conventions across .NET microservices.

Can I generate both single-entity and list queries with paging support using CQRS scaffolding?

Yes, CQRS query scaffolding supports both single-entity and list queries, including built-in paging support for list responses, alongside handler, repository method, and endpoint generation.

Does scaffolding CQRS queries follow OpenAPI metadata conventions automatically?

Yes, scaffolding CQRS queries follows SignalBeam project conventions for naming, structure, and OpenAPI metadata, ensuring generated GET endpoints include proper documentation automatically.

What do I need to scaffold CQRS queries in a SignalBeam architecture .NET project?

You need a .NET project following the SignalBeam architecture with established CQRS patterns. The scaffolding generates query, response, handler, repository method, and endpoint files within the target service.

Why should I use scaffolding for CQRS queries instead of writing handlers and endpoints manually?

Scaffolding CQRS queries speeds up backend feature delivery by ensuring consistent read-model patterns across services, eliminating repetitive boilerplate for handlers, repository methods, and endpoints.