glab-config_skill

This skill helps you manage glab configuration settings, retrieving and updating keys like browser, editor, host, and token to tailor your GitLab CLI.

Python

2.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill glab-config

SKILL.md2.9 KB

Overview

This skill manages glab configuration keys and values to control CLI behavior. It exposes commands to read, write, and edit the glab config file, including common settings like editor, browser, host, token, and display options. Use it to inspect or persist environment-independent preferences for glab.

How this skill works

The skill wraps the glab config subcommands: get, set, and edit. It reads from either the project or global config file, writes key/value pairs, and opens the config in your chosen editor. It respects environment overrides such as $EDITOR, $VISUAL, $BROWSER, and $GLAB_CHECK_UPDATE.

When to use it

Check the current value of a glab configuration key (e.g., host, token, editor).
Persist a preference like pager, browser, or glamour_style across machines.
Switch between project-level and global config using the --global flag.
Open and manually edit the raw glab config file for advanced changes.
Set or update an access token or default host for automated scripts.

Best practices

Prefer using --global for machine-wide defaults and omit it for repository-specific settings.
Keep sensitive values like tokens in environment variables when possible; use config only if necessary and protect the file.
Verify changes with glab config get <key> after running set to avoid typos.
Use your preferred editor via $EDITOR or $VISUAL to ensure the edit subcommand opens correctly.
Document any non-obvious config changes in your project README or onboarding notes.

Example use cases

Set the default editor: glab config set editor vim
View the stored GitLab token: glab config get token
Open the config file for a quick manual tweak: glab config edit
Enable hyperlink display on TTY: glab config set display_hyperlinks true
Switch the default host to a self-hosted instance: glab config set host https://gitlab.example.com

FAQ

Add the --global flag to set or edit to apply values in the global config file.

Will environment variables override config values?

Yes. Environment variables like $EDITOR, $BROWSER, and $GLAB_CHECK_UPDATE take precedence over unset config keys.