release-dotfiles

Verify repository cleanliness and create Git tags and GitHub releases.

9|1|Updated Jul 19, 2022
One-click install
npx skills add https://github.com/benthamite/dotfiles --skill release-dotfiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-dotfiles
Source: https://github.com/benthamite/dotfiles/tree/main/claude/skills/release-dotfiles
Command: npx skills add https://github.com/benthamite/dotfiles --skill release-dotfiles

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of releasing new versions of your dotfiles repository, ensuring that all associated package repositories are in a clean and stable state before a new release is tagged and published.

Core Features & Use Cases

  • Package Repository Verification: Checks local clones of package repositories for uncommitted changes or unpushed commits.
  • Dotfiles Status Check: Ensures the main dotfiles repository itself is clean before proceeding.
  • Version Bumping and Release Notes: Analyzes commit history to suggest semantic version bumps and drafts release notes.
  • Automated Tagging and Publishing: Creates Git tags, pushes them, and creates GitHub releases.
  • Use Case: Before updating your Emacs configuration, you want to ensure all your custom packages are pushed and your dotfiles are clean. This skill automates that verification and the subsequent release process.

Quick Start

Use the release-dotfiles skill to cut a new release for the dotfiles repository.

Frequently Asked Questions about release-dotfiles

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

FAQPage Schema
How do I automate semantic versioning and GitHub releases for my dotfiles repository?

Automating dotfiles releases involves verifying repository cleanliness, analyzing commit history for semantic version bumps, drafting release notes, and creating Git tags and GitHub releases. This requires Git, Emacs, and GitHub CLI.

Can I check if my local package repositories have unpushed commits before releasing my dotfiles?

Yes, verifying package repositories for uncommitted changes or unpushed commits is a core step. Checking local clones ensures all associated packages are clean and stable before a new dotfiles release is tagged and published.

Do I need Emacs installed to automate my dotfiles release process?

Yes, Emacs is required to resolve elpaca profiles during the dotfiles release process. Along with Git and GitHub CLI, Emacs handles package dependencies before tagging and publishing the GitHub release.

What's the best way to draft release notes for a dotfiles repository based on commit history?

Drafting release notes for dotfiles involves analyzing the commit history to suggest appropriate semantic version bumps and generate summaries. This ensures release notes accurately reflect repository changes before creating Git tags.

Why should I verify dotfiles cleanliness before cutting a new version tag?

Verifying dotfiles cleanliness prevents tagging unstable configurations. Ensuring the main repository and associated packages have no uncommitted changes guarantees a stable, reliable release before publishing to GitHub.

Does this release-dotfiles automation work with package managers other than elpaca?

This release automation specifically uses Emacs to resolve elpaca profiles for package repositories. Using package managers other than elpaca is not supported by the current release verification and tagging workflow.