planSettingsLanguage

Name: planSettingsLanguage
Availability: InStock
Author: bekachkhiro

Switch Plan Plugin language preferences across global and local scopes.

1|Updated Jan 26, 2026

Search Tags:#cli #localization #configuration #plugin #language #preferences

Ready to run

npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill plansettingslanguage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planSettingsLanguage
Source: https://github.com/BekaChkhiro/claude-plan-plugin/tree/main/commands/planSettingsLanguage
Command: npx skills add https://github.com/BekaChkhiro/claude-plan-plugin --skill plansettingslanguage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables users to switch language preferences for the Plan Plugin, providing a consistent way to apply language changes across global and per-project scopes.

Core Features & Use Cases

Global and local language updates: change the UI language for all Claude Code interactions or just for the current project.
Persistent configuration: writes language preference to standard config paths so changes persist across sessions.
Use Case: Imagine you work on a team with English and Georgian speakers; you switch the plugin language to match your locale and all prompts update accordingly.

Quick Start

Run the planSettingsLanguage command to switch the language globally.

Use /planSettingsLanguage --local to apply changes for the current project only.

Frequently Asked Questions about planSettingsLanguage

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

FAQPage Schema

How do I switch the Plan Plugin language settings?▼

Switch the Plan Plugin language settings by running the command to update your configuration file, which persists your language preference across sessions. It guides you through selecting a language, saving it to global or local config paths, and confirming the change.

Can I apply localization settings globally or just for the current project?▼

You can apply localization settings globally for all interactions or locally for the current project. Use the default command for global scope or add the --local flag to restrict the configuration update to your current working directory only.

Does the Plan Plugin language configuration persist across sessions?▼

The language configuration persists across sessions because the tool writes your preference to standard configuration paths. It reads existing configuration from local and global paths, updates the file, and displays a confirmation message to verify persistence.

What is the difference between global and local language preferences in plugin configuration?▼

Global language preferences apply to all interactions by updating the global configuration path, while local preferences apply only to your current project by updating a local configuration file. Both read existing settings before applying updates and showing a confirmation message.

How do I update localization preferences for a multilingual development team?▼

Update localization preferences for a multilingual team by running the language switch command to match your locale. The tool reads existing config, updates the file with the new language, and confirms the change so prompts display correctly for English, Georgian, or other supported speakers.