freeshard-change-control

Enforce triage, branch, and release protocols for the Freeshard project.

47|2|Updated Feb 11, 2025
One-click install
npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-change-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeshard-change-control
Source: https://github.com/FreeshardBase/freeshard/tree/main/.claude/skills/freeshard-change-control
Command: npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-change-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in the Freeshard development lifecycle by enforcing strict triage, branch, and release protocols, preventing stalled PRs and production incidents.

Core Features & Use Cases

  • Dev Board Triage: Provides clear guidance on interpreting the Freeshard Dev Board, handling issue pickup, and identifying when to skip vague tasks.
  • Release Discipline: Ensures changes are only considered shipped after proper version bumping, GitHub releases, and controller-side rollouts.
  • Safety Guardrails: Enforces critical operational constraints, such as maintaining Traefik v2, avoiding shell access on shards, and respecting read-only data models.

Quick Start

Use the freeshard-change-control skill to verify if the current issue is ready for development or if it requires further intent capture from the maintainer.

Frequently Asked Questions about freeshard-change-control

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

FAQPage Schema
How do I enforce strict triage and release protocols for a GitHub development workflow?

Enforce strict triage and release protocols by applying standardized branching rules and version-bump procedures to GitHub issue pickup and PR creation, preventing stalled PRs and production incidents.

What is the best way to manage version bumping and GitHub releases for production deployment?

Manage version bumping by ensuring changes are only considered shipped after proper version bumps, GitHub releases, and controller-side rollouts are completed within the maintainer-gated deployment workflow.

How do I triage vague issues on a GitHub dev board before starting development?

Triage vague issues by verifying if the current issue is ready for development or requires further intent capture from the maintainer, skipping tasks that lack clear development intent.

What architectural constraints and safety guardrails must I follow during shard development?

Follow safety guardrails by maintaining Traefik v2, avoiding shell access on shards, and respecting read-only data models to satisfy non-negotiable architectural constraints.

Does the Freeshard release process support maintainer-gated deployment workflows?

The Freeshard release process supports maintainer-gated deployment workflows by enforcing strict release discipline that requires proper version bumping and controller-side rollouts before changes are shipped.

When should I skip a vague task during GitHub issue pickup?

Skip a vague task during GitHub issue pickup when the issue lacks clear intent and requires further intent capture from the maintainer before development can safely proceed.