organize

Automate GitHub issue lock, unlock, pin, unpin, and transfer actions via gh CLI.

2|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ondrasek/cc-plugins --skill organize-ondrasek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/github-issues/skills/organize
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill organize-ondrasek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Administrative operations on GitHub issues that control visibility and lifecycle such as locking, unlocking, pinning, unpinning, and transferring issues.

Core Features & Use Cases

  • Lock Conversation: prevent further comments on an issue with an explanatory comment.
  • Unlock Conversation: re-enable comments on a previously locked issue.
  • Pin/Unpin Issue: highlight important issues with visibility controls, respecting repository pin limits.
  • Transfer Issue: move an issue to another repository while updating references.

Quick Start

Specify the issue number and the desired administrative action (lock, unlock, pin, unpin, or transfer) to perform the operation.

Frequently Asked Questions about organize

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

FAQPage Schema
How do I automate locking and unlocking GitHub issues?

Automating GitHub issue locking and unlocking uses the gh CLI to perform administrative actions, preventing or re-enabling comments on issues with an explanatory comment.

Can I pin and unpin multiple GitHub issues programmatically?

Pinning and unpinning GitHub issues programmatically highlights important issues with visibility controls while respecting repository pin limits through automated gh CLI commands.

What is the best way to transfer GitHub issues to another repository?

Transferring GitHub issues to another repository moves the issue while updating references, executed via the gh CLI to maintain lifecycle management across repositories.

What permissions do I need to manage GitHub issue lifecycle and visibility?

Managing GitHub issue lifecycle and visibility requires maintainer permissions to execute lock, unlock, pin, unpin, and transfer actions via the gh CLI with built-in safeguards.

Why should I use the gh CLI for GitHub issue admin actions?

Using the gh CLI for GitHub issue admin actions provides operational safeguards and batch processing capabilities for maintainers managing visibility and lifecycle across multiple issues.