archive-full

Package git-tracked source files into a tar.gz archive, excluding binaries and build artifacts.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/ahrav/scratch-scanner-rs --skill archive-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive-full
Source: https://github.com/ahrav/scratch-scanner-rs/tree/main/.claude/skills/archive-full
Command: npx skills add https://github.com/ahrav/scratch-scanner-rs --skill archive-full

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps in creating a comprehensive archive of all source code files within a repository, excluding unnecessary build artifacts and binaries, making it ideal for backups or sharing.

Core Features & Use Cases

  • Source Code Archiving: Packages all tracked source files into a single .tar.gz archive.
  • Exclusion of Unwanted Files: Automatically filters out binaries, build outputs, and temporary files.
  • Use Case: Before a major refactor or when preparing a release candidate, you can use this Skill to create a complete, clean snapshot of your project's source code.

Quick Start

Use the archive-full skill to create a tar.gz archive of the entire source code.

Frequently Asked Questions about archive-full

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

FAQPage Schema
How do I package all git tracked source code into a tar.gz archive?

To package source code into a tar.gz archive, this skill targets git-tracked files and compresses them. It automatically filters out common binary extensions, build directories, and generated files to ensure a clean snapshot for backups or distribution.

Does archiving source code automatically exclude binaries and build artifacts?

Yes, archiving source code with this method automatically excludes binaries and build artifacts. It specifically filters out common binary extensions, build directories, and generated files, ensuring only tracked source code is included in the final tar.gz archive.

What is the best way to create a clean source code backup before a refactor?

Creating a clean source code backup before a refactor is best done by packaging git-tracked files into a tar.gz archive. This approach captures a complete source snapshot while excluding unnecessary build outputs and temporary files from the repository.

Can I use this to package only git tracked files for distribution?

Yes, you can use this to package git tracked files for distribution. The skill specifically targets files managed by git, ensuring that untracked local files, binaries, and generated build artifacts are excluded from the final compressed archive.

Why does my source code archive still contain generated files?

If your source code archive contains generated files, they are likely tracked by git. This skill filters common binary extensions and build directories but includes all git-tracked files, so manually untracked or ignored generated files are the only ones excluded.