walnut-manage-repos

Manage Open Walnut repository profiles via a YAML-based registry with CRUD operations.

27|7|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/EvanZhang008/open-walnut --skill walnut-manage-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walnut-manage-repos
Source: https://github.com/EvanZhang008/open-walnut/tree/main/src/data/skills/walnut-manage-repos
Command: npx skills add https://github.com/EvanZhang008/open-walnut --skill walnut-manage-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple project repositories manually leads to scattered data and context loss. This Skill provides a centralized, YAML-based registry to add, view, edit, and remove repository profiles, each storing name, description, tech stack, hosts, architecture notes, and common commands.

Core Features & Use Cases

  • Create, read, update, and delete repository profiles using simple file-based commands.
  • Store structured repo metadata under ~/.open-walnut/repositories/ and reference it during Claude Code sessions.
  • Quickly view or modify repo data to keep project profiles consistent across teams.

Quick Start

Register a new repository profile by providing its name, description, tech stack, and at least one host path, then save it to ~/.open-walnut/repositories/.

Frequently Asked Questions about walnut-manage-repos

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

FAQPage Schema
How do I manage multiple project repositories without losing context?

Manage repository profiles centrally using a YAML-based registry to add, view, edit, and remove repo metadata like tech stack, hosts, and architecture notes. This prevents scattered data and context loss across multiple projects.

What is the best way to store repository architecture notes and common commands in YAML?

Store repository architecture notes and common commands in YAML profiles under the ~/.open-walnut/repositories/ directory. Each profile supports optional fields for overview and common_commands alongside required tech stack and host data.

Can I use file-based commands to update repository profiles for Open Walnut projects?

Yes, you can update repository profiles using file-based CRUD operations accessed via the files_* commands. These commands let you register new repositories and modify existing profile data stored in YAML format.

How do I register a new repository profile with tech stack and host paths?

Register a new repository profile by providing its name, description, tech stack, and at least one host path. The profile is saved as a YAML file under ~/.open-walnut/repositories/ for consistent team access.

Does this YAML registry approach require external dependencies to track repo metadata?

No external dependencies are required to track repo metadata. The registry operates independently using file-based YAML storage and built-in commands to manage structured data like architecture notes and hosts.

Why use a centralized YAML registry instead of manual files for repository metadata?

A centralized YAML registry prevents scattered data by storing all repository metadata in a consistent structure. Unlike manual files, it provides standardized CRUD commands to keep project profiles consistent and accessible across teams.