-
Notifications
You must be signed in to change notification settings - Fork 0
chore(mcps/skills): add shared ticket skills and readme atlassian rovo mcp setup #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jblxo
wants to merge
2
commits into
main
Choose a base branch
from
chore/add-shared-ticket-skills
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,126 @@ | ||
| # Jira MCP | ||
|
|
||
| Setup guide for connecting your agent to Atlassian Rovo MCP for Jira access. | ||
|
|
||
| ## Supports | ||
|
|
||
| - OpenCode | ||
| - Codex | ||
| - Claude Code | ||
| - Cursor | ||
| - JetBrains AI Assistant | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| - Atlassian Cloud site with Jira enabled | ||
| - Access to the Atlassian site you want to use | ||
| - Node.js 18+ | ||
| - `npx` | ||
| - A browser for the OAuth login flow | ||
|
|
||
| ## Server Endpoint | ||
|
|
||
| Use Atlassian's remote MCP server through `mcp-remote`: | ||
|
|
||
| ```text | ||
| https://mcp.atlassian.com/v1/mcp | ||
| ``` | ||
|
|
||
| The first login is handled through Atlassian OAuth in the browser. No local PAT is required for the basic setup below. | ||
|
|
||
| ## Codex | ||
|
|
||
| Add to `~/.codex/config.toml`: | ||
|
|
||
| ```toml | ||
| [mcp_servers.atlassian] | ||
| command = "npx" | ||
| args = ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"] | ||
| ``` | ||
|
|
||
| ## OpenCode | ||
|
|
||
| Add to `~/.config/opencode/opencode.json` or `opencode.jsonc`: | ||
|
|
||
| ```json | ||
| { | ||
| "$schema": "https://opencode.ai/config.json", | ||
| "mcp": { | ||
| "atlassian": { | ||
| "type": "local", | ||
| "command": ["npx", "-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"], | ||
| "enabled": true | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## Claude Code | ||
|
|
||
| Add to `~/.claude.json` for user scope or `.mcp.json` in the repo for project scope: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "atlassian": { | ||
| "command": "npx", | ||
| "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"] | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## Cursor | ||
|
|
||
| Add to `~/.cursor/mcp.json` for global scope or `.cursor/mcp.json` for project scope: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "atlassian": { | ||
| "command": "npx", | ||
| "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"] | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## JetBrains AI Assistant | ||
|
|
||
| In the IDE: | ||
|
|
||
| 1. Open `Settings` | ||
| 2. Go to `Tools | AI Assistant | Model Context Protocol (MCP)` | ||
| 3. Click `Add` | ||
| 4. Choose `STDIO` | ||
| 5. Paste: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "atlassian": { | ||
| "command": "npx", | ||
| "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"] | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ## Verify | ||
|
|
||
| After restart, verify with two prompts: | ||
|
|
||
| - `Find my recent Jira issues` | ||
| - `Open issue ABC-123 and summarize it` | ||
|
|
||
| Expected result: | ||
|
|
||
| - the browser opens an Atlassian login/consent flow on first use | ||
| - Jira issues can be searched and read after login | ||
|
|
||
| ## Notes | ||
|
|
||
| - This uses Atlassian's hosted MCP endpoint, proxied by `mcp-remote` | ||
| - Access is limited by the signed-in Atlassian user's permissions | ||
| - The same server can also expose Confluence and other Atlassian products, but this guide is focused on Jira support for our ticket skills | ||
| - If your org blocks MCP usage, an Atlassian admin may need to allow it first |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| # pr-ready | ||
|
|
||
| Review current work, run the required verification, prepare the branch, create a commit if the work is ready, and stop before push by default. | ||
|
|
||
| ## What It Does | ||
|
|
||
| - reviews the current changes for bugs, regressions, and missing verification | ||
| - runs the required repository verification or the smallest meaningful checks | ||
| - fixes small directly related issues when appropriate | ||
| - creates or keeps a suitable branch | ||
| - creates a commit when the work is genuinely ready | ||
| - pushes only if the user explicitly asks for it | ||
|
|
||
| ## Requires | ||
|
|
||
| - a git repository | ||
| - enough local tooling to run the repository verification commands | ||
|
|
||
| ## Install | ||
|
|
||
| Install from the shared repo with `skills.sh`: | ||
|
|
||
| ```bash | ||
| npx skills add https://github.com/eManPrague/agent-tooling --skill pr-ready | ||
| ``` | ||
|
|
||
| ## Example Prompts | ||
|
|
||
| ```text | ||
| Prepare the current changes for PR. Use pr-ready. | ||
| ``` | ||
|
|
||
| ```text | ||
| Review, verify, commit, and push this branch if everything passes. Use pr-ready. | ||
| ``` | ||
|
|
||
| ## Intended Behavior | ||
|
|
||
| - review first | ||
| - verify before commit | ||
| - commit only when genuinely ready | ||
| - do not push unless explicitly asked | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,126 @@ | ||
| --- | ||
| name: pr-ready | ||
| description: > | ||
| Review current work, run the required project verification, create or keep a | ||
| suitable branch, commit the ready changes, and stop before push with a clear | ||
| status summary. If the user explicitly asks for push, push only after review, | ||
| verification, branch preparation, and commit have succeeded. | ||
| --- | ||
|
|
||
| # PR Ready | ||
|
|
||
| Prepare current work for PR or MR review. | ||
|
|
||
| ## Input | ||
|
|
||
| Accept one of: | ||
|
|
||
| - current working tree | ||
| - current branch | ||
| - explicit scope from the user | ||
|
|
||
| If the branch or scope is ambiguous, ask one short clarification question. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Inspect the current git state. | ||
| 2. Review the changes for bugs, regressions, and missing verification. | ||
| 3. Run the required verification for the repository. | ||
| 4. Fix small review or verification issues when they are directly actionable. | ||
| 5. If the work is ready, create or keep a suitable branch. | ||
| 6. Commit the relevant changes. | ||
| 7. If and only if the user explicitly asked for push, push the branch. | ||
| 8. Report what succeeded, what failed, and what should happen next. | ||
|
|
||
| ## Review Rules | ||
|
|
||
| - Default to a code review mindset. | ||
| - Look for bugs, behavioral regressions, risky edge cases, and missing validation. | ||
| - Keep the review practical. | ||
| - If you find a small fix that is clearly part of the same work, implement it. | ||
| - If you find a larger blocker, stop and report it instead of forcing a commit. | ||
|
|
||
| ## Verification Rules | ||
|
|
||
| - Run the required verification for the repository if defined. | ||
| - Otherwise run the smallest meaningful verification for the changed area. | ||
| - Report every command you ran and whether it passed or failed. | ||
| - If verification fails, fix what is reasonable and rerun the relevant checks. | ||
| - If failures remain, do not create a misleading ready commit. | ||
|
|
||
| ## Branch Rules | ||
|
|
||
| - If already on a sensible feature branch, keep it. | ||
| - If on the default branch, detached HEAD, or an obviously unsuitable branch, create a new branch first. | ||
| - If a new branch is needed, infer naming from repository conventions when possible. | ||
| - Otherwise use a short descriptive branch name. | ||
| - Do not push the branch unless the user explicitly asked for it. | ||
|
|
||
| ## Commit Rules | ||
|
|
||
| - Commit only when the work is genuinely ready based on the review and verification outcome. | ||
| - Stage only the relevant changes. | ||
| - Do not include unrelated files. | ||
| - Infer commit message conventions from repository history or documented conventions when possible. | ||
| - Do not bypass hooks. | ||
| - Do not amend unless the user explicitly asks, or a hook modified files from the commit you just created and they need to be included. | ||
|
|
||
| ## Push Rules | ||
|
|
||
| - Default behavior is no push. | ||
| - Push only when the user explicitly asks for it. | ||
| - Push only after the work is genuinely ready. | ||
| - Do not force push unless the user explicitly asks for it. | ||
| - Report whether push happened or was intentionally skipped. | ||
|
|
||
| ## Stop Conditions | ||
|
|
||
| Stop without committing when: | ||
|
|
||
| - review found a meaningful unresolved blocker | ||
| - required verification is still failing | ||
| - the work is not clear enough to commit safely | ||
|
|
||
| In that case, report the blockers and the next action. | ||
|
|
||
| ## Output | ||
|
|
||
| Return the result in this structure. | ||
|
|
||
| ### Review | ||
| - key findings or `No blocking findings` | ||
|
|
||
| ### Verification | ||
| - commands run | ||
| - pass/fail for each | ||
|
|
||
| ### Branch | ||
| - current branch kept or new branch created | ||
| - branch name | ||
|
|
||
| ### Commit | ||
| - commit created or not created | ||
| - commit hash and message if created | ||
|
|
||
| ### Ready To Push | ||
| - `Yes` or `No` | ||
|
|
||
| ### Push | ||
| - pushed or not pushed | ||
| - remote branch name if pushed | ||
| - if not pushed, state whether it was skipped by default or waiting for user confirmation | ||
|
|
||
| ### Failed Or Blocked | ||
| - remaining failures or blockers | ||
| - if none, say so explicitly | ||
|
|
||
| ### Next Actions | ||
| - short actionable list for the user | ||
|
|
||
| ## Constraints | ||
|
|
||
| - Keep the flow simple. | ||
| - Do not push unless the user explicitly asks. | ||
| - Do not create a PR or MR unless the user asks. | ||
| - Do not commit unrelated changes. | ||
| - Ask at most one clarification question if the branch or scope is ambiguous. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,46 @@ | ||||||||||||||||||
| # ticket-analysis | ||||||||||||||||||
|
|
||||||||||||||||||
| Analyze a ticket or issue from a URL or ID and return an implementation-ready analysis without changing code. | ||||||||||||||||||
|
|
||||||||||||||||||
| ## What It Does | ||||||||||||||||||
|
|
||||||||||||||||||
| - detects the issue tracker from URL, ID, and repository context | ||||||||||||||||||
| - fetches the ticket using the best available MCP or local tooling | ||||||||||||||||||
| - maps the request to the current codebase | ||||||||||||||||||
| - returns a concrete analysis with the next recommended step | ||||||||||||||||||
|
|
||||||||||||||||||
| ## Requires | ||||||||||||||||||
|
|
||||||||||||||||||
| Tracker access must already be configured. | ||||||||||||||||||
|
|
||||||||||||||||||
| Supported sources include: | ||||||||||||||||||
|
|
||||||||||||||||||
| - Atlassian MCP for Jira and Confluence | ||||||||||||||||||
| - GitLab MCP for GitLab issues | ||||||||||||||||||
| - GitHub MCP or `gh` for GitHub issues | ||||||||||||||||||
|
|
||||||||||||||||||
| ## Install | ||||||||||||||||||
|
|
||||||||||||||||||
| Install from the shared repo with `skills.sh`: | ||||||||||||||||||
|
|
||||||||||||||||||
| ```bash | ||||||||||||||||||
| npx skills add https://github.com/eManPrague/agent-tooling --skill ticket-analysis | ||||||||||||||||||
|
Comment on lines
+24
to
+27
|
||||||||||||||||||
| Install from the shared repo with `skills.sh`: | |
| ```bash | |
| npx skills add https://github.com/eManPrague/agent-tooling --skill ticket-analysis | |
| Install from the shared repo: | |
| ```bash | |
| npx skills add https://github.com/jblxo/agent-tooling --skill ticket-analysis |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Install section references
skills.sh, but there is noskills.shin this repo, and the command shown usesnpx skills .... Also the repo URL should be consistent with the canonical URL used in other skill READMEs (currentlymr-resolvepoints at a different owner). Please align the wording and URL so the install instructions don’t break.