Skip to content

feat(skills): add jira-cli, jira-comment skill and setup script - #15

Open
svg153 wants to merge 3 commits into
masterfrom
feat/jira-cli-global-skills
Open

svg153 wants to merge 3 commits into
masterfrom
feat/jira-cli-global-skills

Conversation

@svg153

@svg153 svg153 commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Context

jira-cli (ankitpokhrel) is installed at C:\Users\sergio.valverde\tools\jira-cli\bin and on the user PATH. The agent skills that make it usable only existed inside a private workspace, so they could not be used from any other repo.

This PR publishes only workspace-agnostic material.

Changes

  • .ai/skills/jira-cli — official ankitpokhrel/jira-cli agent skill (machine-readable output, config-as-data-source, safe execution).
  • .ai/skills/add-comment-jira-cloud — rich-formatted Jira Cloud comments via the Atlassian MCP, with the HTML/ADF catalogue.
  • .ai/scripts/setup-jira-cli.ps1 — interactive, idempotent setup for jira-cli on Windows. The site URL is a mandatory parameter; no host, project key or board name is baked in.
  • .gitignore — keeps local-only skills out of version control.

Deliberately excluded

Two skills stay local and git-ignored because they carry a site URL, a cloudId and internal issue keys:

  • the board-context skill
  • the weekly-report generator

They remain fully functional on the machine that owns that context.

Notes

  • No credentials anywhere: the API token lives in the user-scoped JIRA_API_TOKEN environment variable (or %USERPROFILE%\_netrc), never in the repo.
  • ~/.copilot/skills is a junction to .ai/skills, so the published folders are live immediately on the machine that has them.

svg153 and others added 3 commits October 15, 2026 10:28
Copilot only discovers skills shaped as <name>/SKILL.md with YAML
frontmatter, and the three <name>.skill.md files sitting directly in
.ai/skills were never loaded: they started at '# Skill: ...' with no
frontmatter at all. Each one now lives in its own folder with name and
description frontmatter, and the document body is untouched (git sees
them as renames at 87-92% similarity).

Also brings in three skills that only existed outside the repo
(grill-me, grilling, web-design-guidelines) so .ai/skills is a complete
superset of ~/.copilot/skills. That directory is about to be replaced by
a junction pointing here, and anything missing would silently disappear.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Workspace-agnostic additions only:

- .ai/skills/jira-cli: official ankitpokhrel/jira-cli agent skill (machine-readable
  output, config-as-data-source, safe execution).
- .ai/skills/add-comment-jira-cloud: rich-formatted Jira Cloud comments via the
  Atlassian MCP.
- .ai/scripts/setup-jira-cli.ps1: interactive setup for jira-cli. The site URL is a
  mandatory parameter; no client host, project key or board name is baked in.
- .gitignore: keeps local-only skills out of version control.

Project-specific board context and the weekly-report generator stay local and
git-ignored: they carry a site URL, a cloudId and internal issue keys.
…ted at rest

HKCU\Environment is plain text: any process running as the user can read it, and it
leaks into registry exports. This script encrypts the token with DPAPI, which binds
the ciphertext to the current Windows user account on this machine.

- Writes %LOCALAPPDATA%\jira\token.dpapi (not synced to OneDrive, ACL restricted).
- -InstallProfileHook adds an idempotent, secret-free block to the PowerShell profile
  that decrypts the blob into JIRA_API_TOKEN on every new shell.
- -RemoveRegistryVariable deletes the plain-text copy once the store is verified.
- Round-trip check decrypts and compares before reporting success.
- Ciphertext is trimmed on read: DPAPI rejects a trailing newline.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant