skills.rest
matteobortolazzo
matteobortolazzoCOMMUNITY
Explore all skills by this author →
GitHub

ticket-ownership

Assign GitHub issues exclusively after validating user identity and existing assignees.

1|Updated Mar 24, 2026
Search Tags:#automation#workflow#collaboration#github#cli#issue tracking
One-click install
npx skills add https://github.com/matteobortolazzo/cenci --skill ticket-ownership
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-ownership
Source: https://github.com/matteobortolazzo/cenci/tree/main/flow/skills/ticket-ownership
Command: npx skills add https://github.com/matteobortolazzo/cenci --skill ticket-ownership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents collaborative conflicts by ensuring that only one developer is assigned to a GitHub issue, maintaining clear accountability during the development lifecycle.

Core Features & Use Cases

  • Conflict Prevention: Automatically checks for existing assignees to avoid overwriting or duplicating work.
  • Identity Verification: Validates the current GitHub user against the repository's active session.
  • Safe Mutation: Provides a controlled, gate-checked mechanism to claim unassigned issues only after explicit authorization.

Quick Start

Invoke the ticket-ownership skill to verify and claim the current GitHub issue for the active user.

Frequently Asked Questions about ticket-ownership

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

FAQPage Schema
How do I prevent concurrent work conflicts on GitHub issues?▼

To prevent concurrent work conflicts on GitHub issues, you need a mechanism that checks for existing assignees before applying mutations. This ensures exclusive assignment and maintains clear accountability during the development lifecycle.

How does GitHub issue ownership verification work?▼

GitHub issue ownership verification works by validating the current active GitHub user against the repository's active session. It performs read-only inspections using the GitHub CLI to check existing assignees before safely applying authorized issue edits.

Do I need the GitHub CLI to automate issue assignment?▼

Yes, you need the GitHub CLI installed and authenticated to automate issue assignment. The system requires it to perform read-only inspections of existing assignees and to execute authorized issue edits safely.

Can I use this workflow to claim already assigned GitHub issues?▼

No, you cannot claim already assigned GitHub issues with this workflow. It provides a controlled, gate-checked mechanism designed to claim unassigned issues only, preventing the overwriting or duplicating of work.

What is ticket-mode workflow for issue tracking?▼

Ticket-mode workflow for issue tracking is a process that manages exclusive assignment of GitHub issues. It validates user identity and checks for existing assignees before applying mutations to prevent collaborative conflicts.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
mcj-codermcj-coder
1

requirements-gathering

Gather requirements through interactive questioning and create structured tickets.

Community
Advanced
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
eysenfalkeysenfalk

github-project-management

Manage GitHub projects with AI swarm coordination for issue tracking and sprint planning.

Community
Advanced