fetch-stacks

Detect stacks from SessionStart hooks and copy convention files into .claude/rules.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill fetch-stacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-stacks
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/fetch-stacks
Command: npx skills add https://github.com/dotBeeps/pantry --skill fetch-stacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull stack convention files for the current project by running detection heuristics from SessionStart hooks.

Core Features & Use Cases

  • Auto-detect stacks from SessionStart hooks and copy .md files into .claude/rules
  • Optional: fetch a specific stack by name when provided
  • Falls back to ~/.claude/<stack-name>.md if the stack file is not found via hooks
  • Supports parallel copying to speed up refresh operations

Quick Start

Run /fetch-stacks to load all detected stacks into .claude/rules, or specify a stack name to fetch a specific one.

Frequently Asked Questions about fetch-stacks

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

FAQPage Schema
How do I load stack convention files into my project automatically?

Load stack convention files by running detection heuristics from SessionStart hooks, which auto-detect stacks and copy the corresponding .md files into .claude/rules. You can trigger this by running /fetch-stacks to pull all detected stacks into your project.

Can I fetch a specific stack by name instead of loading all detected stacks?

Fetch a specific stack by providing its name as an argument to the command. The tool parses the stack slug, searches the local hook registry, and copies that specific stack's convention files into the .claude/rules directory.

What happens if a stack file is not found via SessionStart hooks?

When a stack file is not found via hooks, the tool falls back to ~/.claude/<stack-name>.md. This ensures your development workflow continues with default stack conventions even if the hook detection misses the file.

Does fetch-stacks create the .claude/rules directory if it is absent?

Yes, the tool creates the .claude/rules directory if it is absent during the file copying process. This ensures stack convention files are always copied successfully into your current project workspace without manual setup.

How do I speed up stack convention refresh operations for multiple stacks?

Speed up stack convention refresh operations using the tool's parallel copying feature. This allows multiple detected stack files to be copied into .claude/rules simultaneously, significantly reducing the time needed for bulk workspace setup.