gather-project-metadata

Extracts metadata for use in generating a document preamble or a formatted code block.

10|2|Updated Dec 23, 2025

Search Tags:#automation #git #documentation #repository #metadata #frontmatter #timestamp

Ready to run

npx skills add https://github.com/eveld/claude --skill gather-project-metadata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gather-project-metadata
Source: https://github.com/eveld/claude/tree/main/skills/gather-project-metadata
Command: npx skills add https://github.com/eveld/claude --skill gather-project-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture and standardize essential project metadata for documentation frontmatter, ensuring consistent timestamps, commit hashes, branches, repository paths, project names, and feature slugs.

Core Features & Use Cases

Collects current timestamp, git commit hash, branch name, repository name, project name, and feature slug (where applicable) for documentation frontmatter.
Provides a ready-to-paste YAML frontmatter payload and a script-based workflow to gather data from the current repo.
Supports both automated script execution and manual data collection for flexible workflows across multiple repositories.

Quick Start

Run the metadata collection script at ~/.claude/scripts/collect-metadata.sh to generate a ready frontmatter payload for insertion into your documents.

Frequently Asked Questions about gather-project-metadata

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

FAQPage Schema

How do I collect git metadata for YAML frontmatter in documentation?▼

To collect git metadata for YAML frontmatter, this skill extracts commit hash, branch name, repository name, and timestamp from your current repository. It provides a ready-to-paste YAML payload for insertion into research notes and release docs.

What project metadata fields are needed for consistent documentation frontmatter?▼

Standard project metadata fields for documentation frontmatter include current timestamp, git commit hash, branch name, repository path, project name, and feature slug. This skill standardizes these fields across multiple repositories and feature directories.

Can I use a script to automate repository metadata collection for release docs?▼

Yes, you can automate repository metadata collection for release docs by running the provided metadata collection script. It generates a ready frontmatter payload by gathering data from the current repo environment, supporting automated script execution workflows.

Does this metadata collection tool require access to package.json or the directory structure?▼

Yes, this metadata collection tool requires access to the current Git repository and the project's directory structure or package.json to determine the project name. It uses this access to gather accurate repository and project metadata fields.

What's the best way to standardize timestamps and commit hashes across multiple repository docs?▼

The best way to standardize timestamps and commit hashes across multiple repository docs is using a script-based workflow that extracts consistent metadata fields. This skill supports both automated script execution and manual data collection for flexible workflows.