gdk

name	gdk
description	Handle GitLab Development Kit updates, local secrets, and GDK branch workflows. Use for fgdku-based updates, setting up GitLab secrets, managing branch-specific GDK state, and other local GitLab development environment operations.
license	MIT
compatibility	opencode
metadata	{"audience":"developers","author":"pedropombeiro","keywords":"gdk, gitlab-development-kit, update, secrets, environment","workflow":"gitlab"}

GDK Skill

Shell functions for managing the GitLab Development Kit: full update orchestration, switching to main branch cleanly, and setting up API tokens from 1Password.

All functions are zsh functions loaded from ~/.shellrc/zshrc.d/functions/.

Available Commands

fgdku

Comprehensive GDK update orchestrator. Performs the full update cycle:

1. Restores bin/rake, bin/rspec, bin/rails, bin/spring, db/structure.sql, package.json
2. Prompts to reset if there are uncommitted changes
3. Resets network adapter if network is unreachable
4. Installs mise tools and ensures the gdk gem is available
5. Stops Spring, restarts PostgreSQL, runs gdk update
6. Reinstalls bundle and regenerates Spring binstubs
7. Runs a simple rspec test to bring up Gitaly
8. Runs pending ClickHouse migrations
9. Rebases all local branches, then prunes those whose tip is reachable from master
10. Switches back to the original branch
11. Runs gdk cleanup, truncates large logs, restarts GDK
12. Enables db sandbox, regenerates schema if branch migrations exist
13. Warms up Rails environment

run-in-tmux-pane fgdku

Reports progress via iTerm2 badges and Home Assistant webhooks. Must be run via run-in-tmux-pane since it is an autoloaded zsh function and is long-running/interactive. Set the Bash tool timeout to at least 1800000 ms (30 min).

gswm

Switches to the main branch, restoring db/ and package.json first and resetting the GDK sandbox if inside a GDK directory.

gswm

setup_gitlab_secrets

Fetches GITLAB_TOKEN, GITLAB_STAGING_TOKEN, and GITLAB_GDK_TOKEN from 1Password and exports them as environment variables.

setup_gitlab_secrets

Requires 1Password CLI (op) and a gitlab account configured.

Agent Guidelines

1. Never update from remote manually — do not run git pull, git fetch + git rebase, or gdk update directly in a GDK repo. Always use run-in-tmux-pane fgdku instead; it handles fetching, rebasing all branches, bundle install, migrations, GDK restart, and post-update cleanup in the correct order
2. fgdku is interactive and long-running — always run via run-in-tmux-pane fgdku; it prompts on uncommitted changes so do not run without user confirmation
3. Use gswm when the user wants to return to main branch cleanly (safer than plain git switch)
4. setup_gitlab_secrets requires biometric auth — cannot be run non-interactively
5. GDK_ROOT must be set — gswm and fgdku check $GDK_ROOT to determine if they're in a GDK directory