skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

start-ticket

Declare an active ticket to permit gated code edits.

Updated Apr 15, 2026
Search Tags:#workflow#claude#ticket#gate#code-edit#marker#ops-fork
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill start-ticket-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start-ticket
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/start-ticket
Command: npx skills add https://github.com/AAbdulghany/fms --skill start-ticket-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage editing permissions by declaring an active ticket so code edits are gated by a per-project marker in the ops fork.

Core Features & Use Cases

  • Creates a per-project or ops-level marker in .claude/session to permit edits only under allowed paths, and supports switching tickets by overwriting the marker.
  • Derives the target scope from the input format (owner/repo#N or plain N) and selects per-project vs ops fallback behavior based on tracker registry.
  • Integrates with the Pre-Build Gate workflow to enforce ticket existence before touching source, docs, or infra.

Quick Start

Run the start-ticket command with a ticket reference to activate an editing ticket.

Frequently Asked Questions about start-ticket

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

FAQPage Schema
How do I gate code edits so changes only happen when an active ticket exists?▼

You can gate code edits by declaring an active ticket that writes a per-project marker in the ops fork's .claude/session structure, enforcing ticket existence before touching source or infra.

What is a Pre-Build Gate workflow for managing editing permissions?▼

A Pre-Build Gate workflow enforces ticket existence before touching source, docs, or infra by requiring a valid ticket marker to permit code edits across managed repositories.

How do I activate an editing ticket using the owner/repo#N format?▼

To activate an editing ticket, run the start command with an owner/repo#N or plain N reference, which derives the target scope and selects per-project or ops fallback behavior based on the tracker registry.

Can I switch active tickets without removing the existing code edit marker?▼

Yes, you can switch tickets by overwriting the existing marker. The skill supports switching active tickets by replacing the per-project or ops-level marker in the session structure.

Does the ticket gating workflow apply to both per-project and ops-level repositories?▼

The ticket gating workflow applies to both per-project and ops-level workflows across managed repositories, resolving the marker path and enforcing marker creation within the ops fork's .claude/session structure.

Why do my code edits fail when no active ticket marker is declared?▼

Code edits fail without an active ticket marker because the gating hooks enforce ticket existence before allowing changes, requiring a valid marker to be written in the session structure.

Related Skills

Explore More Software Engineering Skills→
me2reshme2resh
489

start-ticket

...

Community
Intermediate
T-ravT-rav
5

hf.gate-stop-agents

Check for a code-changed marker before allowing agent reviews to proceed.

Community
Basic
willdadywilldady
63

wayfinder

Decomposes high-level objectives into a hierarchical structure of issue-tracker tickets.

Community
Advanced
T-ravT-rav
5

hf.track-exploration

Record per-session markers for Read and Grep exploration actions.

Community
Basic