Skip to content

feat(skill): summarize jira issues & PR reviews#26

Open
andrew-ronaldson wants to merge 3 commits intopatternfly:mainfrom
andrew-ronaldson:pr-review-summary
Open

feat(skill): summarize jira issues & PR reviews#26
andrew-ronaldson wants to merge 3 commits intopatternfly:mainfrom
andrew-ronaldson:pr-review-summary

Conversation

@andrew-ronaldson
Copy link
Copy Markdown

@andrew-ronaldson andrew-ronaldson commented Mar 18, 2026

summarize-issues
This Skill pulls information from the Atlassian MCP and provides a summary of tasks for a user.

The output outlines tasks by priority and makes recommendations on how to approach the workload.

Further exploration will be done in a follow up to refine the skill outputs

summarize-pr-reviews
This skill takes all PRs that are awaiting your review and gives a quick summary of the changes, time to review and recommended order.

…ributions. Enhanced description and workflow steps to prioritize active sprint tasks, fetch contributor issues, and provide a sprint-focused summary output.
@andrew-ronaldson andrew-ronaldson changed the title feat(skill): summarize jira issues feat(skill): summarize jira issues & PR reviews Mar 19, 2026
@@ -0,0 +1,243 @@
---
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skills need to live under plugins/<plugin-name>/skills/ to be discovered — .cursor/skills/ isn't the right location. These are workflow/project management skills, so plugins/pf-workflow/skills/summarize-issues/ would be the right home.

@@ -0,0 +1,289 @@
---
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above — needs to move to plugins/pf-workflow/skills/summarize-pr-reviews/.


First, get the user's Atlassian account info and accessible resources.

```
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The exact MCP tool calls with full parameter lists are over-prescribing implementation — the AI already knows how to use these tools. Describing the intent in plain language (e.g. "query active sprint issues assigned to the current user, ordered by priority") and letting the AI figure out the tool calls would keep this shorter and more maintainable.

First, get the authenticated GitHub user's information.

```
get_me()
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same pattern here — the exact search_issues() and get_pull_request() calls with parameters could be replaced with plain language intent like "find open PRs requesting my review, sorted by most recently updated."

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.

2 participants