sitemaps-generate

Regenerate landing and docs sitemap XML from git commit timestamps.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill sitemaps-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sitemaps-generate
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/sitemaps-generate
Command: npx skills add https://github.com/clawperator/clawperator --skill sitemaps-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Regenerate landing and docs sitemap metadata from per-URL source files using each file's last git commit timestamp, then validate the resulting XML and build integration.

Core Features & Use Cases

  • Landing sitemap generation from a deterministic manifest
  • Sitemap index lastmod values based on child sitemap source changes
  • Docs sitemap lastmod and priority patching after MkDocs build
  • Git-based timestamps using each source file's own last commit time
  • Pre-commit freshness for locally modified source files

Quick Start

Run the sitemap generator to refresh landing and docs sitemaps from the repository sources.

Frequently Asked Questions about sitemaps-generate

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

FAQPage Schema
How do I generate sitemap lastmod values from git commit timestamps?

Sitemap lastmod values are generated by extracting the last git commit timestamp for each per-URL source file and applying it to the corresponding sitemap XML entry. This ensures deterministic timestamping directly aligned with source code changes.

Can I patch docs sitemap metadata automatically after an MkDocs build?

Docs sitemap metadata can be patched after an MkDocs build by updating lastmod and priority fields based on the source files. The generator applies git-based timestamps to align the built documentation pages with freshness expectations.

How do landing sitemap entries work with a deterministic manifest?

Landing sitemap entries are generated from a deterministic manifest that maps URLs to their source files. The sitemap index lastmod values are then calculated based on the child sitemap source changes reflected in each manifest entry.

Does this sitemap generator validate the XML output and build integration?

The sitemap generator validates the resulting XML output and verifies the build integration after regenerating metadata. This ensures the landing and docs sitemaps remain structurally correct and aligned with GEO expectations following repository updates.

How do I handle pre-commit freshness for locally modified sitemap source files?

Pre-commit freshness for locally modified source files is handled by applying current timestamps to changed files before they are committed. This ensures the generated sitemap metadata accurately reflects uncommitted local modifications during repository maintenance workflows.