What problem does it solve? Engineers repeatedly write ad hoc curl commands and shell-wrapped gh literals to look up Cisco Jira issues and Cisco GHE pull requests, which scatters auth handling, host configuration, and query scope across sessions. This Skill replaces those one-off commands with narrow, validated helper subcommands that keep auth profiles, hosts, and repo boundaries explicit. ## Core Features & Use Cases - Jira Issue Lookup: Read one Cisco Jira issue's stable metadata, or fetch it together with comments and attachments, using a fixed bearer-token auth profile on jira-eng-gpk2.cisco.com. - Cisco GHE PR Inspection: View a single PR, search closed PRs inside one repo, or map a commit SHA to the PRs that contain it on sqbu-github.cisco.com. - Strict Scope Guardrails: Helpers reject non-https Jira URLs, foreign hosts, arbitrary auth env names, and repo/org/user query qualifiers that would override the explicit --repo boundary. - Use Case: Before starting diagnosis on a bug, fetch the Jira issue's metadata and comments, then map the suspect commit SHA to its originating PRs to confirm which change introduced the regression. ## Quick Start Ask the assistant to look up the Cisco Jira issue SPARK-786996 with its comments and attachments using the cisco-trackers-lookup helper before starting diagnosis.
