dev-test-and-release

Automate a standardized dev-to-release workflow for homelab projects.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/carter2099/.dotfiles-homelab --skill dev-test-and-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-test-and-release
Source: https://github.com/carter2099/.dotfiles-homelab/tree/main/.claude/skills/dev-test-and-release
Command: npx skills add https://github.com/carter2099/.dotfiles-homelab --skill dev-test-and-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes a repeatable dev-to-release workflow across homelab projects, reducing drift and approval delays.

Core Features & Use Cases

  • Workspace-first approach: work in ~/dev/<repo> while deployment artifacts live in ~/<app>/ (e.g. ~/delta_neutral/, ~/blog/).
  • Stepwise process: setup workspace, do the work, verify and show, release, and deploy in project-specific idioms.
  • Collaboration and governance: promotes formal approvals before release and uses the project's own conventions for versioning and release.

Quick Start

Clone the target repo into ~/dev/<repo> and follow the Step 1–Step 3 workflow to prepare a release candidate.

Frequently Asked Questions about dev-test-and-release

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

FAQPage Schema
How do I standardize a dev-to-release workflow for homelab projects?

You can automate a dev-to-release workflow by following a stepwise process: setup the workspace in ~/dev/<repo>, verify changes, seek formal approval, and release using the project's own idioms to reduce delays.

How do I automate code review approvals before releasing a project?

Automate code review approvals by promoting formal approvals before release, using the project's own conventions for versioning to ensure governance and reduce approval delays.

What is the best way to separate dev workspaces from deployment artifacts?

Separate workspaces using a workspace-first approach: clone target repos into ~/dev/<repo> for development work while deployment artifacts live in separate ~/<app>/ directories.

Can I use this dev workflow automation for small team projects?

Yes, this workflow automation suits small teams and single-node homelab projects, providing standardized release processes, formal approval governance, and project-specific versioning conventions.

Does this workflow automation handle version control and release processes?

Yes, it handles version control and release processes by encoding deterministic commands and safety checks in SKILL.md, utilizing the project's own idioms for versioning and release.

What limitations exist when automating release processes for homelab setups?

Limitations include its focus on single-node homelab setups or small teams, relying on the project's own idioms for release rather than providing universal deployment scripts.