skills.rest
marin-community
marin-communityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

archive-experiments

Create dated Git tags and update GitHub issues for archived experiment scripts.

1.2k|146|Updated Mar 22, 2024
Search Tags:#git#github issues#archive#repository management#code cleanup#experiments
One-click install
npx skills add https://github.com/marin-community/marin --skill archive-experiments
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archive-experiments
Source: https://github.com/marin-community/marin/tree/main/.agents/skills/archive-experiments
Command: npx skills add https://github.com/marin-community/marin --skill archive-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps maintain a clean and organized repository by archiving old experiment scripts, preventing clutter while preserving their history and accessibility.

Core Features & Use Cases

  • Tagging Commits: Creates date-based Git tags to snapshot archived code.
  • Issue Referencing: Posts canonical comments on GitHub issues linking to archived code.
  • Cleanup: Removes old, redundant tags to maintain a single source of truth for archives.
  • Use Case: When experiment scripts become outdated, use this skill to tag the relevant commit with archive/YYYYMMDD and leave a note on the corresponding GitHub issue, directing future users to the archived location.

Quick Start

Use the archive-experiments skill to tag the current commit as archive/20251114 and update issue 102 with the new archive location.

Frequently Asked Questions about archive-experiments

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

FAQPage Schema
How do I archive legacy experiment scripts in a Git repository?▼

To archive legacy experiment scripts, you create date-based Git tags like archive/YYYYMMDD on the relevant commit. This snapshots the historical code while keeping your active repository clean and free of outdated clutter.

What is the best way to link archived code to GitHub issues?▼

The best way to link archived code to GitHub issues is by posting canonical comments on the corresponding issue. This references the dated Git tag, directing future users directly to the archived experiment location.

Do I need GitHub CLI to tag commits and update issues?▼

Yes, you need authenticated GitHub CLI installed alongside local Git access. These tools are required to programmatically create the dated repository tags and post the referencing comments to GitHub issues.

How does repository cleanup handle redundant Git tags?▼

Repository cleanup handles redundant Git tags by removing old ones to maintain a single source of truth. This ensures only the correct dated archive references remain accessible without causing tag clutter.

When should I archive repository experiments instead of deleting them?▼

You should archive repository experiments instead of deleting them when scripts become outdated but must remain accessible. Archiving preserves the development history via Git tags while maintaining active workspace cleanliness.

Related Skills

Explore More Software Engineering Skills→
gqf2008gqf2008

github-auth

Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.

Community
Intermediate
benthamitebenthamite
9

release-dotfiles

Verify repository cleanliness and create Git tags and GitHub releases.

Community
Advanced
NourcineAbNourcineAb

github-project-management

Automate GitHub issue tracking, board synchronization, and sprint planning workflows.

Community
Advanced
tubtrbtubtrb

release-tagging

Automate release tagging, merged-branch cleanup, and codex/next synchronization from main.

Community
Intermediate