stash-comment

Stash project comments and export patch backups for cross-device restoration.

Updated Mar 3, 2025
One-click install
npx skills add https://github.com/LZY2333/LZY-FE-JumpTrack --skill stash-comment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stash-comment
Source: https://github.com/LZY2333/LZY-FE-JumpTrack/tree/main/agent-configs/skills/custom-stash-comment
Command: npx skills add https://github.com/LZY2333/LZY-FE-JumpTrack --skill stash-comment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project-level explanations and notes out of VCS history by stashing comments, exporting patch backups, and enabling cross-device restoration.

Core Features & Use Cases

  • Stash project comments to separate them from code changes without polluting commit history.
  • Export patch files for backup and transfer to another machine, then apply to restore context.
  • Maintain a centralized log (.comment-stash-log.md) of changes for audit and collaboration.

Quick Start

Invoke the stash-comment workflow to stash current code comments and export a patch for cross-device restoration.

Frequently Asked Questions about stash-comment

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

FAQPage Schema
How do I stash code comments to keep them out of git history?

To stash code comments out of git history, this skill automates storing project-level explanations using git stash, separating contextual notes from code changes without polluting the commit log.

What is the best way to sync project comments across multiple machines?

Syncing project comments across machines relies on exporting patch files for backup and transfer, allowing you to apply the patch on another device to restore the contextual notes.

How do I export a git stash patch to restore context on another device?

Exporting a git stash patch is handled by the workflow which creates patch files from stashed comments, enabling cross-device restoration by applying the patch to the target local repository.

Do I need a local repository to use the stash-comment workflow?

Yes, a local repository is required to use the stash-comment workflow, as it depends on a configured git stash workflow and a central log file to track changes and audit commentary.

How does the centralized comment log work for code review collaboration?

The centralized comment log works by maintaining a .comment-stash-log.md file that tracks stashed comment changes, providing an audit trail for collaborative codebases and personal projects.