fs-release

Automates version bump, commit, push, GitHub release, CI monitoring, and deployment.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/fergus/job-tracker --skill fs-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fs-release
Source: https://github.com/fergus/job-tracker/tree/main/.claude/skills/fs-release
Command: npx skills add https://github.com/fergus/job-tracker --skill fs-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end release process for a software project, reducing manual toil and synchronization errors across versioning, version control, CI, and deployment.

Core Features & Use Cases

  • Version bump and commit in all relevant files
  • Create a GitHub release and monitor CI until it finishes
  • Deploy to test or production environments once CI succeeds

Quick Start

Trigger a full release workflow for the next version, including bump, commit, push, GitHub release, CI wait, and deployment.

Frequently Asked Questions about fs-release

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

FAQPage Schema
How do I automate a full software release from version bump to deployment?

Automating a full release involves triggering a workflow that performs version bumps, Git commits and pushes, creates a GitHub release, monitors CI build status, and deploys to target environments. This eliminates manual toil across versioning, CI, and deployment.

What is end-to-end release automation and how does it handle CI monitoring?

End-to-end release automation orchestrates versioning, source control, and deployment into a single workflow. It handles CI monitoring by creating a GitHub release, tracking the CI build status until completion, and proceeding to deployment only after CI succeeds.

Do I need a configured Git repository and GitHub access to automate releases?

Yes, automating releases requires a configured Git repository, GitHub access for creating releases, and CI integration to monitor build status. These prerequisites ensure the workflow can commit version bumps, push changes, and track deployment readiness.

Can I deploy to both test and production environments after CI succeeds?

Yes, the release workflow can deploy to test or production environments once CI succeeds. It monitors the CI build status continuously and only triggers the environment deployment after confirming the build finished successfully.

What's the best way to reduce manual toil and synchronization errors during versioning and deployment?

The best way to reduce manual toil and synchronization errors is to implement end-to-end release automation. By automating version bumps, commits, pushes, GitHub releases, and CI monitoring together, you ensure every step stays synchronized without manual intervention.

When should I not use an automated release workflow for my project?

You should avoid automated release workflows if your project lacks a configured Git repository, GitHub access, or CI integration. Without these dependencies, the workflow cannot monitor CI status or create the GitHub releases required for deployment.