How do I update the cache if I change my git remote?

You can refresh the cache by deleting the local cache.md file or asking Claude to re-detect the provider, which triggers a fresh scan of your remotes.

Does this skill work with private Bitbucket workspaces?

Yes, it specifically extracts Bitbucket workspace and repository names from the remote URL to ensure correct API targeting.

Where is the git-workflow cache file stored?

The cache is stored locally inside your project repository at .claude/jc-marketplace/git-workflow/cache.md, ensuring settings are project-specific.

Which git providers are automatically detected?

The skill can automatically identify GitHub, GitLab, and Bitbucket based on your repository's remote URL.

Git Workflow Cache Manager

Name: Git Workflow Cache Manager
Author: julien92

byjulien92

•

Developer Tools

Optimizes git-workflow performance by managing local provider detection and persistent repository-level cache storage.

About

The Git Workflow Cache Manager is a specialized skill for Claude Code designed to streamline version control integrations. By automatically detecting git providers like GitHub, GitLab, and Bitbucket from remote URLs, it stores configuration data in a project-local cache to eliminate redundant detection steps during development. This skill ensures that Claude maintains the correct context for repository-specific actions, handles complex Bitbucket workspace metadata, and provides developers with tools to refresh or debug provider settings directly within their local workspace.

Key Features

1 GitHub stars
Specialized Bitbucket workspace and repository metadata extraction
Automatic git provider detection (GitHub, GitLab, Bitbucket)
Project-local cache storage within the .claude directory
Standardized YAML cache format for easy debugging
Manual cache refresh and reset capabilities for remote changes

Use Cases

Configuring Bitbucket-specific environments for automated git tasks
Updating cached provider information after switching repository remotes
Resolving 'not cached' status in git-workflow command contexts

About

Key Features

1 GitHub stars
Specialized Bitbucket workspace and repository metadata extraction
Automatic git provider detection (GitHub, GitLab, Bitbucket)
Project-local cache storage within the .claude directory
Standardized YAML cache format for easy debugging
Manual cache refresh and reset capabilities for remote changes

Use Cases

Configuring Bitbucket-specific environments for automated git tasks
Updating cached provider information after switching repository remotes
Resolving 'not cached' status in git-workflow command contexts