...
npx skills add https://github.com/me2resh/apexyard --skill start-ticket-me2resh
Please help me install this Agent Skill. Skill: start-ticket Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/start-ticket Command: npx skills add https://github.com/me2resh/apexyard --skill start-ticket-me2resh
This Skill solves the problem of blocked code edits when the ticket-first workflow gate is enforced, so you can proceed with safe, production-ready changes tied to an active tracker item.
require-active-ticket.sh PreToolUse hook to permit Edit/Write on permitted code paths..claude/session/tickets/<project> when the ticket’s repo is registered; otherwise uses the ops fallback marker at .claude/session/current-ticket.Start an active coding session by running /start-ticket apexyard#41.
High-intent search queries and answers about installing and using this skill.
To unblock code edits under a ticket-first workflow gate, you must declare an active tracker item tied to the appropriate repository scope. This generates a session marker that permits subsequent Edit and Write operations on validated code paths.
A session marker is a key/value metadata file written to your ops fork that records the active ticket's repo, number, title, URL, suggested branch, and start time. It enables ticket-first development by allowing PreToolUse hooks to validate and permit code editing actions.
Yes, you can use GitHub issues to validate and start a multi-project coding session. The system parses your provided issue identifier, verifies its existence and open state via the configured tracker adapter, and resolves the correct per-project marker path if the repo is registered.
To start an active coding session, run the start command followed by the repository and issue number, such as typing /start-ticket apexyard#41. This validates the GitHub issue, resolves the ops-fork session marker path, and writes the necessary metadata to unblock code editing.
Yes, ticket validation works with trackers other than GitHub issues. You can configure alternative tracker adapters such as Linear, Jira, Asana, or a custom integration to verify issue existence and state before writing the session marker.
For unregistered repositories in a multi-project SDLC, session markers are stored in an ops fallback marker located at .claude/session/current-ticket. Registered repos use a per-project marker under .claude/session/tickets/<project>.
memyselfandmAuto-detect the active PM tool and load the correct adapter.
AAbdulghanyDeclare an active ticket to permit gated code edits.
wsxwj123Enforce edit governance in Claude Code projects with PreToolUse hooks.
JmarquesCreate a shared issue map on an issue tracker for incremental project resolution.