agent-issues

Manage GitHub Issues and machine-wide lockctl locks across repositories.

1|Updated Nov 13, 2023
One-click install
npx skills add https://github.com/LeoTechPro/intTools --skill agent-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-issues
Source: https://github.com/LeoTechPro/intTools/tree/main/codex/assets/codex-home/skills/agent-issues
Command: npx skills add https://github.com/LeoTechPro/intTools --skill agent-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of GitHub Issues and machine-wide locks, ensuring consistent project tracking and preventing conflicts without manual intervention.

Core Features & Use Cases

  • GitHub Issue Management: Create, update, and close GitHub Issues using the GitHub CLI.
  • Machine-Wide Locking: Utilize lockctl to manage resource locks, preventing concurrent modifications and ensuring data integrity.
  • Use Case: When working on a new feature, this Skill can create a GitHub Issue, acquire a lock on the relevant files using lockctl, and track your progress, ensuring no other process interferes.

Quick Start

Use the agent-issues skill to open a new GitHub issue for the current project.

Frequently Asked Questions about agent-issues

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

FAQPage Schema
How do I automate GitHub issue management from the command line?

Automate GitHub issue management by using this Skill to create, update, and close issues directly via the GitHub CLI. It detects your project context from the current working directory to ensure consistent tracking without manual repository configuration.

How does lockctl prevent concurrent file modifications during development?

lockctl prevents concurrent modifications by acquiring machine-wide resource locks on relevant files. This mechanism ensures deterministic task execution and protects data integrity when multiple processes attempt to interact with the same project resources.

Do I need a specific project configuration to manage GitHub issues with this tool?

Managing GitHub issues requires project context detection from your current working directory and adherence to AGENTS.md policies. You must have the GitHub CLI installed and configured to execute issue creation and lock management commands.

What is the best way to track feature progress using GitHub issues and file locks?

Track feature progress by opening a GitHub issue for the current project and acquiring a lock on relevant files using lockctl. This approach links your worklogs and closures directly to the issue while preventing other processes from interfering.

Can I use this workflow to close GitHub issues and release locks automatically?

Yes, you can close GitHub issues and manage lock releases across any repository. The Skill integrates GitHub CLI commands with lockctl to handle worklogs, closures, and resource protection deterministically during your workflow.

What happens if my project lacks an AGENTS.md file for issue creation?

Issue creation and lock management require adherence to AGENTS.md policies. If your project lacks this file, the deterministic task execution and policy compliance needed for safe issue tracking and resource protection will not be enforced.