skills.rest
paulchiu
paulchiuCOMMUNITY
Explore all skills by this author →
GitHub

worktree-tilt-schema

Modify a Tiltfile in a git worktree to boot NestJS and regenerate schema.gql.

3|1|Updated Jun 20, 2016
Search Tags:#devops#schema#graphql#worktree#nestjs#tilt#regeneration
One-click install
npx skills add https://github.com/paulchiu/dotfiles --skill worktree-tilt-schema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worktree-tilt-schema
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/worktree-tilt-schema
Command: npx skills add https://github.com/paulchiu/dotfiles --skill worktree-tilt-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Temporarily modify a Tiltfile in a git worktree to allow the NestJS service to boot and regenerate the GraphQL schema when the local schema.gql becomes stale due to changes in decorators or worktree constraints.

Core Features & Use Cases

  • Adjust Tiltfile behavior in worktree contexts to prevent resource duplication and circular upstream includes during schema regeneration.
  • Provide a safe workflow that reverts Tiltfile changes and restores upstream configurations after regenerating schema.gql.
  • Guides you through ensuring dependent services are running and verifying the regenerated schema.

Quick Start

Regenerate the GraphQL schema in your NestJS project by booting Tilt in the worktree and verifying the updated schema.gql.

Frequently Asked Questions about worktree-tilt-schema

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

FAQPage Schema
How do I regenerate a stale GraphQL schema in a NestJS project using a git worktree?▼

Yes, a stale schema.gql causes NestJS boot failures in worktrees because upstream Tiltfile includes and outdated schemas conflict, requiring temporary Tiltfile modifications to successfully regenerate the GraphQL schema.

Why does my NestJS service fail to boot in a git worktree with an outdated schema.gql?▼

A stale schema.gql causes NestJS boot failures in worktrees because upstream Tiltfile includes and outdated schemas conflict, requiring temporary Tiltfile modifications to successfully regenerate the GraphQL schema.

How do I prevent circular upstream includes in Tilt when running schema regeneration?▼

Prevent circular upstream includes during schema regeneration by selectively disabling those upstream Tiltfile includes before booting the NestJS service, which avoids resource duplication while allowing schema.gql to rebuild safely.

Does modifying the Tiltfile for schema regeneration permanently affect my upstream configuration?▼

No, modifying the Tiltfile for schema regeneration is a safe, temporary workflow that automatically reverts the disabled upstream includes and restores the original configuration after the new schema.gql is generated.

Can I use this schema regeneration workflow if my worktree has dependent services that need to be running?▼

Yes, the schema regeneration workflow supports worktrees with dependencies by guiding you through ensuring dependent services are running in Tilt before booting the NestJS app to regenerate and verify schema.gql.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
proyecto26proyecto26
83

prisma

Manage PostgreSQL schemas, migrations, and queries with Prisma ORM.

Official
Advanced
liatrio-labsliatrio-labs
2

tilt-dev

Verify Tilt service status and retrieve logs for local development environments.

Official
Intermediate
harshvardhan-singh-dhakadharshvardhan-singh-dhakad

firebase-data-connect

Connect Firebase projects to a PostgreSQL-backed GraphQL backend.

Community
Advanced