Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

dev-workflow

Estrelas20

Forks0

Atualizado26 de julho de 2026 às 11:40

Development workflow commands for the Guren monorepo. Handles building packages, running tests (smart targeted or full suite), type checking, pre-PR validation, E2E tests, and dev server startup. Use when user says "build", "test", "typecheck", "type check", "run tests", "test my changes", "quick test", "pr check", "pre-PR", "ready for PR", "dev server", "start server", "e2e", "E2E", "end to end", "playwright".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

gurenjs

gurenjs/guren

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name

dev-workflow

description

Development Workflow Skill

You are a development workflow assistant for the Guren framework monorepo.

Your Role

Help users run builds, tests, type checks, and development servers with intelligent error diagnosis.

Commands

Build

Build all packages in the correct dependency order.

bun run build

The order is derived from each package's dependencies/peerDependencies, so new packages (plugins included) are picked up without editing any script. Print it with:

bun run build:list

Single package:

bun run build server  # @guren/server
bun run build orm     # @guren/orm
bun run build cli     # @guren/cli

On failure: Identify the failing package and show the TypeScript/build error. The issue is usually in that package's src/ directory.

Test

Two modes: smart (targeted) and full.

Smart Test (default for "test my changes", "quick test")

Get changed files:

git diff --name-only HEAD
git diff --name-only --cached

Map to packages:
- packages/server/ → bun test packages/server
- packages/orm/ → bun test packages/orm
- packages/cli/ → bun test packages/cli
- packages/testing/ → bun test packages/testing
- examples/blog/ → bun run test:examples
- examples/api/ → bun run test:examples
Decision logic:
- < 3 files in same package → run package tests
- Multiple packages changed → run affected packages
- 10 files or cross-cutting → run full suite
- No test impact detected → skip tests
After smart tests pass, remind: "Consider running full suite before PR: bun run test"

Full Test Suite (default for "run tests", "test")

bun run test

Runs:

bun run test:bun — Framework tests. The package list is discovered from packages/* (every package whose test script uses Bun's runner), so new packages need no wiring. bun run test:bun:list prints it; bun run test:bun <pkg> narrows it.
bun run test:examples — Example app tests (blog, api)
bun run test:testing — @guren/testing only (vitest, so not part of test:bun)

On failure: Identify the failing test file and test name, show the error, suggest fixes.

Type Check

bun run typecheck

Runs root monorepo + blog example type checks.

On failure: List each error with file:line, show the message, suggest fixes for common issues (missing types, incorrect imports, type mismatches).

PR Check (pre-PR validation)

Run all checks in order. Stop and report on first failure:

bun run build && bun run typecheck && bun run test

On success, confirm:

All packages built successfully
No type errors found
All tests passing

E2E Tests (default for "e2e", "playwright", "end to end")

Runs Playwright E2E tests against the blog example app.

Prerequisites: Database running + migrated + seeded, packages built, dev server NOT already running (Playwright starts its own).

cd examples/blog && bun run e2e

Opens Playwright UI for debugging:

cd examples/blog && bun run e2e:ui

Known flaky tests:

Validation tests (Inertia XHR round-trip timing) are flaky in CI. They are skipped via test.skip(!!process.env.CI) but may occasionally fail locally too. If only validation tests fail, it is safe to proceed.

On failure:

Check if the failure is a known flaky test (validation spec)
If not, check the error screenshot in examples/blog/test-results/
Ensure the database is running and seeded: bun run db:up && bun run db:migrate && bun run db:seed

Dev Server

Start the blog example development server.

bun run dev

Available at http://localhost:3333

Prerequisites check before starting:

Database running? If not: bun run db:up
Migrations applied? If not: bun run db:migrate
Packages built? If not: bun run build

Package Test Commands

Package	Command
Server	`bun test packages/server`
ORM	`bun test packages/orm`
CLI	`bun test packages/cli`
Testing	`bun test packages/testing`
Core	`bun test packages/core`
Create App	`bun test packages/create-app`
Examples	`bun run test:examples`
All	`bun run test`

Mais deste repositório

mesmo repositório

db-manage

gurenjs/guren

Database management for Guren with safety checks. Handles migrations, rollbacks, seeding, resets, and container management. Use when user mentions "database", "migration", "migrate", "rollback", "seed", "reset", "db:up", "db:down", "db:reset", "fresh database", or database-related tasks.

2026-07-2620

dev-workflow

gurenjs/guren

Development workflow commands for a Guren application. Handles dev server startup, building, testing, type checking, and pre-deploy validation. Use when user says "build", "test", "typecheck", "type check", "run tests", "dev server", "start server", "deploy check", "pre-PR", "ready for PR", "ci check". For database operations like migrations, rollbacks, and seeding, use the db-manage skill instead.

2026-07-2620

feature

gurenjs/guren

Generate a complete CRUD feature with all related components in one workflow — Model, Controller, Views, Routes, Tests, Factory, Seeder, Resource. Use when user wants to build out an entire entity at once. Triggers include "full feature", "CRUD", "resource for", "complete setup", "everything for", "build out the X feature", "scaffold everything for", or mentions an entity name with the intent of creating all components (e.g., "I need a Product entity"). For creating a single component, use the scaffold skill instead.

2026-07-2320

scaffold

gurenjs/guren

Generate individual Guren framework components using bunx guren make:* CLI commands. Creates a single component at a time — controllers, models, views, middleware, jobs, events, listeners, mail, tests, resources, factories, seeders, providers, commands, exceptions, channels, notifications, migrations, routes. Use when user says "create a controller", "generate a model", "scaffold middleware", "make a job", "add a job", "new event", "make middleware", "make:controller", or asks for a single new component. For generating all components for an entity at once, use the feature skill instead.

2026-07-2320

plugin-authoring

gurenjs/guren

Install or author Guren plugins — npm packages that extend a Guren app via the ServiceProvider system. Use when the user asks to "install a plugin", "add @guren/plugin-*", "create a plugin", "build a Guren plugin", "make:plugin", or wants a reusable package that registers services, middleware, or CLI commands into a Guren app.

2026-07-2120

guren-api

gurenjs/guren

Guren framework API documentation, code patterns, and examples. Covers all subsystems — Controllers, Models, Routes, Middleware, Authentication, Authorization, Events, Jobs, Queue, Mail, Cache, Validation, Broadcasting, Notifications, Storage, Scheduling, I18n, Encryption, Health Checks, Error Handling, Container/ServiceProvider, Console Commands, and API Resources. Use when user asks "how to", "how does", "example of", "what is", or needs help understanding any Guren API.

2026-07-2120

name

dev-workflow

description

Development Workflow Skill

You are a development workflow assistant for the Guren framework monorepo.

Your Role

Help users run builds, tests, type checks, and development servers with intelligent error diagnosis.

Commands

Build

Build all packages in the correct dependency order.

bun run build

The order is derived from each package's dependencies/peerDependencies, so new packages (plugins included) are picked up without editing any script. Print it with:

bun run build:list

Single package:

bun run build server  # @guren/server
bun run build orm     # @guren/orm
bun run build cli     # @guren/cli

On failure: Identify the failing package and show the TypeScript/build error. The issue is usually in that package's src/ directory.

Test

Two modes: smart (targeted) and full.

Smart Test (default for "test my changes", "quick test")

Get changed files:

git diff --name-only HEAD
git diff --name-only --cached

Map to packages:
- packages/server/ → bun test packages/server
- packages/orm/ → bun test packages/orm
- packages/cli/ → bun test packages/cli
- packages/testing/ → bun test packages/testing
- examples/blog/ → bun run test:examples
- examples/api/ → bun run test:examples
Decision logic:
- < 3 files in same package → run package tests
- Multiple packages changed → run affected packages
- 10 files or cross-cutting → run full suite
- No test impact detected → skip tests
After smart tests pass, remind: "Consider running full suite before PR: bun run test"

Full Test Suite (default for "run tests", "test")

bun run test

Runs:

bun run test:bun — Framework tests. The package list is discovered from packages/* (every package whose test script uses Bun's runner), so new packages need no wiring. bun run test:bun:list prints it; bun run test:bun <pkg> narrows it.
bun run test:examples — Example app tests (blog, api)
bun run test:testing — @guren/testing only (vitest, so not part of test:bun)

On failure: Identify the failing test file and test name, show the error, suggest fixes.

Type Check

bun run typecheck

Runs root monorepo + blog example type checks.

On failure: List each error with file:line, show the message, suggest fixes for common issues (missing types, incorrect imports, type mismatches).

PR Check (pre-PR validation)

Run all checks in order. Stop and report on first failure:

bun run build && bun run typecheck && bun run test

On success, confirm:

All packages built successfully
No type errors found
All tests passing

E2E Tests (default for "e2e", "playwright", "end to end")

Runs Playwright E2E tests against the blog example app.

Prerequisites: Database running + migrated + seeded, packages built, dev server NOT already running (Playwright starts its own).

cd examples/blog && bun run e2e

Opens Playwright UI for debugging:

cd examples/blog && bun run e2e:ui

Known flaky tests:

Validation tests (Inertia XHR round-trip timing) are flaky in CI. They are skipped via test.skip(!!process.env.CI) but may occasionally fail locally too. If only validation tests fail, it is safe to proceed.

On failure:

Check if the failure is a known flaky test (validation spec)
If not, check the error screenshot in examples/blog/test-results/
Ensure the database is running and seeded: bun run db:up && bun run db:migrate && bun run db:seed

Dev Server

Start the blog example development server.

bun run dev

Available at http://localhost:3333

Prerequisites check before starting:

Database running? If not: bun run db:up
Migrations applied? If not: bun run db:migrate
Packages built? If not: bun run build

Package Test Commands

Package	Command
Server	`bun test packages/server`
ORM	`bun test packages/orm`
CLI	`bun test packages/cli`
Testing	`bun test packages/testing`
Core	`bun test packages/core`
Create App	`bun test packages/create-app`
Examples	`bun run test:examples`
All	`bun run test`