Using GitHub CLI (gh)

Automate GitHub issue creation and searching using the GitHub CLI (gh) with commands like `gh issue create` and `gh issue list`. The CLI handles authentication, repository context, and output formatting, eliminating manual web interface work and enabling scripted workflows for duplicate detection and bulk operations.

Yes, use `gh issue list` with search flags across repositories. Combine with `jq` to filter and format results by status, assignee, labels, or custom criteria, enabling cross-repository issue tracking and automation without writing custom API clients.

Install the GitHub CLI (gh) and authenticate with `gh auth login` to set token scopes. Ensure your environment has correct repository context and jq installed for data parsing. Verify token permissions support the operations—issue creation, PR management, or repository queries—you plan to automate.

Use `gh` output flags like `--json` to specify fields, then pipe to `jq` for filtering, transformation, and export. This produces structured data for reporting, notifications, or integration with other tools, avoiding manual parsing and ensuring reliable field selection.

Common issues include incorrect repository context, insufficient token scopes, and unspecified output fields causing silent failures. The Skill covers environment-aware scripting, explicit field selection, and token validation to ensure reusable, reliable automation across different machines and CI/CD contexts.

Yes, `gh` automates querying repository metadata, labels, and activity logs programmatically. Replace repetitive web browsing with scripted commands to access and update repository state, enabling efficient bulk operations and integration into larger automation workflows.