archive-src

Creates a source-only tar.gz archive from src/, tests/, and Cargo.toml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for a lean, source-code-focused archive of a project, ideal for uploads or checkpoints where only essential code and tests are required, reducing file size and simplifying management.

Core Features & Use Cases

  • Selective Archiving: Packages only the src/ and tests/ directories, along with Cargo.toml.
  • Exclusion of Unnecessary Files: Intentionally omits build artifacts, documentation, configuration files, and CI/CD related content.
  • Use Case: Quickly create a compact backup of your project's core logic and test suite before a major refactor or for submission to a code review platform that has size limitations.

Quick Start

Run the archive-src skill to create a source-only tar.gz archive of the current project.

Frequently Asked Questions about archive-src

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

FAQPage Schema
How do I create a minimal source code archive for a Rust project?

To create a minimal source code archive, package only the src/ and tests/ directories along with Cargo.toml into a compact .tar.gz file. This excludes build artifacts and configuration, producing a lean checkpoint for uploads.

What is the best way to exclude build artifacts when creating a tar.gz backup of source code?

The best way to exclude build artifacts from a tar.gz backup is by selectively archiving only the src/, tests/, and Cargo.toml files. This intentionally omits documentation, configuration, and CI files to minimize file size.

Can I use this archiving method for code review submissions with size limits?

Yes, you can use this archiving method for code review submissions with size limits. By excluding unnecessary files like build artifacts and CI configurations, it produces a compact .tar.gz file containing only essential code.

Does this source-only archive include Cargo.toml and test files?

Yes, this source-only archive includes Cargo.toml and test files. It selectively packages the tests/ directory alongside the src/ directory to ensure your core logic and test suite are preserved in the checkpoint.

What files are omitted when creating a source-only checkpoint?

When creating a source-only checkpoint, omitted files include build artifacts, documentation, configuration files, and CI/CD related content. Only the src/ directory, tests/ directory, and Cargo.toml are packaged into the archive.

When should I not use a minimal source-only archive?

You should not use a minimal source-only archive when your upload or checkpoint requires documentation, configuration files, or CI/CD content. This approach strictly packages src/, tests/, and Cargo.toml, excluding all other project files.