10x-archive

Archive completed changes by moving folders and updating status.

Updated Jun 9, 2024
One-click install
npx skills add https://github.com/Kuba312/daily-board --skill 10x-archive-kuba312
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-archive
Source: https://github.com/Kuba312/daily-board/tree/main/frontend/.agents/skills/10x-archive
Command: npx skills add https://github.com/Kuba312/daily-board --skill 10x-archive-kuba312

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes by automating folder movement, updating status, and optionally closing roadmap items.

Core Features & Use Cases

  • Automated Folder Movement: Moves completed change folders to the archive directory and stamps the change.md file with an archived status.
  • Status Update: Updates the change.md file with the archived status and the date of archiving.
  • Roadmap Item Closure: Optionally closes the corresponding roadmap item if it exists.
  • Use Case: After completing a change, use this Skill to ensure that the change is properly archived and any related roadmap items are updated.

Quick Start

Archive a completed change by running the command: /10x-archive <change-id>

Frequently Asked Questions about 10x-archive

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

FAQPage Schema
How do I automate archiving completed changes with git mv and roadmap updates?

Automating change archiving involves moving completed change folders to an archive directory and stamping the change.md file with an archived status and date. This process uses git mv and git add commands to handle file operations and optionally close corresponding roadmap items.

What is the best way to update change status and close roadmap items after completion?

Updating change status and closing roadmap items is best handled by stamping the change.md file with an archived status and archiving date. This automated status update ensures that any related roadmap items are optionally closed when the change folder is moved to the archive directory.

Do I need a specific folder structure to archive changes and update roadmap files?

You need access to the specific change folder containing your change.md file and the roadmap file to archive changes properly. The archiving process relies on moving these existing folders to an archive directory and executing git operations to track the changes.

Does change archiving work with standard git operations for file movement?

Yes, change archiving works directly with standard git operations by executing commands like git mv and git add for file movement. This ensures that folder movement to the archive directory and status updates are tracked correctly in your version control history.

Can I close roadmap items automatically when moving change folders to an archive?

You can automatically close roadmap items when moving change folders to an archive by running the archiving command. The process optionally closes the corresponding roadmap item in the roadmap file if it exists while updating the change.md status.