cxc-ast-grep
FreeUse for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
The English summary is being prepared. Showing the original description.
Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Ownership boundary: This skill owns API design, app architecture, database optimization, error handling, middleware, queues, long-lived connections, and app-level observability/health hooks. Deployment strategy, rollback proof, rollout shape, SLOs, alert routing, incident response, and operational readiness gates are owned by
dev-devops. Backend exposes the app-level hooks that DevOps operational gates consume.
Build reliable, secure, and maintainable server-side applications. This skill is a routing role that activates by change-surface: whenever the work primarily touches APIs, servers, services, jobs, data access, schemas, migrations, or operational backend behavior, use this skill and then read the relevant references.
Before backend work, read dev for classification, fast paths, rule authority, family invariants, verification, and safety; current/public evidence follows its Conditional Routes.
| Condition | Reference |
|---|---|
| C2 ordinary CRUD/resource slice | CRUD API alone suffices |
| New/changed API style or C3+ API work | API design |
| Versioning, deprecation, or API migration | API lifecycle |
| Stack detection, ambiguous technology, or architecture/protocol selection | Setup; C3+: Architecture |
| New endpoints, classes, or modules | Anti-slop |
| SSE/WebSocket, runtime timeouts/drain/request IDs, or async queues | Connections and queues |
| Layer placement, error mapping/Result, middleware order, or response contracts | Request contracts |
| Caching, observability, template evaluation, performance, SEO, handoff, or delivery checklist | Production delivery |
| Production/long-lived services | Observability, health checks |
| CPU-bound/untrusted work | Process isolation |
| Cache optimization | Caching patterns |
| Node/TypeScript, Python, or database work | Node, Python, database, respectively |
| ML deployment, RAG/LLM integration, or mobile APIs | ML serving, LLM integration, mobile API, respectively |
| Auth/input/security policy | cxc-dev-security |
| Deployment, analytics, frontend contracts, testing, RCA, or scaffolding | Handoff owners |
Read api-design.md + anti-slop-backend.md first, then the relevant stack file.
For C2 ordinary slices, crud-api.md alone suffices; read api-design.md/architecture.md for new API styles or C3+ work.
For error mapping and the conditional Result pattern, read Error handling.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
The English summary is being prepared. Showing the original description.
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
The English summary is being prepared. Showing the original description.
Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
The English summary is being prepared. Showing the original description.
Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.
The English summary is being prepared. Showing the original description.
Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.
The English summary is being prepared. Showing the original description.
Use for debugging and system comprehension. Triggers: debug this, root cause, how does X work, reverse engineer, 왜 안 돼, 디버깅, 원인 분석, 로직 파악, 뜯어봐.
The English summary is being prepared. Showing the original description.