plugin-cache
Git-workflow plugin cache management. Use when Provider cache shows "not cached" to detect and cache the git provider. Also use to understand cache format or refresh cached values.
What this skill does
# Git-workflow Plugin Cache This skill manages the provider cache for git-workflow commands. The cache stores auto-detected provider information to avoid re-detection on each command. ## When to use this skill - Provider cache shows "not cached" in a command's Context - User asks to refresh or reset the git provider detection - User switches remote or needs to change the cached provider - Understanding cache format for debugging ## Cache location The cache file is stored **in the current repository**, not in the user's home directory: ``` <repository-root>/.claude/jc-marketplace/git-workflow/cache.md ``` **IMPORTANT:** This is a project-local file (`.claude/` relative to the git repository root), NOT `~/.claude/` in the home directory. ## Cache format ```yaml --- provider: github|gitlab|bitbucket bitbucket_workspace: <workspace> # Bitbucket only bitbucket_repo: <repo> # Bitbucket only --- # Git Workflow Cache Auto-detected on <date>. Provider: **<provider>** ``` ## Creating the cache ### Step 1: Detect provider from Remote URL | URL contains | Provider | |--------------|----------| | `github` | `github` | | `gitlab` | `gitlab` | | `bitbucket` | `bitbucket` | | none of the above | Ask user to choose | ### Step 2: Extract Bitbucket info (if applicable) For Bitbucket, extract workspace and repo from the remote URL: | URL format | Workspace | Repo | |------------|-----------|------| | `[email protected]:myworkspace/myrepo.git` | `myworkspace` | `myrepo` | | `https://bitbucket.org/myworkspace/myrepo.git` | `myworkspace` | `myrepo` | ### Step 3: Create cache directory and write file **CRITICAL: The exact path must be `.claude/jc-marketplace/git-workflow/cache.md`** Do NOT use: - `~/.claude/...` (home directory) - `.claude/cache.md` (missing subdirectories) - `.claude/git-workflow.local.md` (wrong filename) First, create the directory structure: ```bash mkdir -p .claude/jc-marketplace/git-workflow ``` Then, use the Write tool to create the file at this exact path: ``` .claude/jc-marketplace/git-workflow/cache.md ``` **Example:** If repository is at `/home/user/myproject`, the cache file must be: ``` /home/user/myproject/.claude/jc-marketplace/git-workflow/cache.md ``` ### Step 4: Verify cache was created correctly After writing the file, verify it exists at the correct path: ```bash cat .claude/jc-marketplace/git-workflow/cache.md ``` If this command fails or shows a different file, you created the cache in the wrong location. Delete the wrong file and retry Step 3. ### Step 5: Continue After verification succeeds, continue with the original command. ## Refreshing the cache Delete the cache file (in the repository root) and re-run any git-workflow command: ```bash rm "$(git rev-parse --show-toplevel)/.claude/jc-marketplace/git-workflow/cache.md" ``` ## Example Remote URL: `[email protected]:myteam/my-project.git` Cache file content: ```markdown --- provider: bitbucket bitbucket_workspace: myteam bitbucket_repo: my-project --- # Git Workflow Cache Auto-detected on 2025-01-15. Provider: **bitbucket** ```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.