feat(skill): summarize jira issues & PR reviews#26
feat(skill): summarize jira issues & PR reviews#26andrew-ronaldson wants to merge 4 commits intopatternfly:mainfrom
Conversation
…ributions. Enhanced description and workflow steps to prioritize active sprint tasks, fetch contributor issues, and provide a sprint-focused summary output.
andrew-ronaldson
changed the title
| @@ -0,0 +1,243 @@ | |||
| --- | |||
There was a problem hiding this comment.
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 @@ | |||
| --- | |||
There was a problem hiding this comment.
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. | ||
|
|
||
| ``` |
There was a problem hiding this comment.
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() |
There was a problem hiding this comment.
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."
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
📝 WalkthroughWalkthroughTwo new skill specification files introduced: Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Verification against CONTRIBUTING-SKILLS.md and Anthropic skill-creator plugin standards; workflow coherence and API integration accuracy. Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (2)
.cursor/skills/summarize-issues/SKILL.md (1)
1-1:⚠️ Potential issue | 🟠 MajorRelocate this skill to the plugin skills tree.
Placing it in
.cursor/skills/...conflicts with the repo’s documentedplugins/<plugin-name>/skills/...layout for contributed skills.Based on learnings: "Applies to plugins/*/skills/** : Create a directory under the plugin's
skills/folder with the patternplugins/<plugin-name>/skills/your-skill/when adding a skill to an existing plugin".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.cursor/skills/summarize-issues/SKILL.md at line 1, The summarize-issues skill (SKILL.md) is in the global .cursor skills tree but must live under a plugin's skills tree; move the "summarize-issues" SKILL.md into the target plugin’s skills directory by creating a new folder for the skill under that plugin’s skills area (e.g., <plugin>-skills/your-skill/), place SKILL.md there, and update any references or exports that point to ".cursor/skills/summarize-issues/SKILL.md" so they reference the new plugin-scoped location; ensure the skill directory name remains "summarize-issues" and metadata in SKILL.md (if any) is unchanged..cursor/skills/summarize-pr-reviews/SKILL.md (1)
1-1:⚠️ Potential issue | 🟠 MajorMove this skill under
plugins/<plugin-name>/skills/for discovery.This file location (
.cursor/skills/...) does not match the repo’s skill placement convention and may prevent normal plugin discovery workflows.Based on learnings: "Applies to plugins/*/skills/** : Create a directory under the plugin's
skills/folder with the patternplugins/<plugin-name>/skills/your-skill/when adding a skill to an existing plugin".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.cursor/skills/summarize-pr-reviews/SKILL.md at line 1, The SKILL.md for the "summarize-pr-reviews" skill is placed under .cursor/skills which breaks plugin discovery; move the skill into your plugin's skills directory by creating plugins/<plugin-name>/skills/summarize-pr-reviews/ and relocating SKILL.md there (and update any internal references or imports to point to the new location) so the skill follows the plugins/*/skills/** discovery pattern.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.cursor/skills/summarize-issues/SKILL.md:
- Line 22: Several fenced code blocks in SKILL.md lack language labels causing
MD040 failures; add appropriate fence labels (e.g., text, jql, json, bash)
immediately after each opening ``` for the blocks referenced (lines noted in the
review: 22, 34, 45, 60, 82) so markdownlint recognizes the language and improves
readability—edit each ``` to ```text or ```jql (or another suitable language)
depending on the block content.
- Line 235: Replace the phrase "High priority backlog" with the hyphenated
compound adjective "High-priority backlog" in the document; locate the exact
occurrence shown in the diff (the line containing **High priority backlog (not
in sprint):**) and update it to **High-priority backlog (not in sprint):** to
correct hyphenation.
In @.cursor/skills/summarize-pr-reviews/SKILL.md:
- Line 21: Multiple fenced code blocks in SKILL.md trigger markdownlint MD040
because they lack language identifiers; update each triple-backtick fence (``` )
used throughout the document — including the occurrences noted around the
examples — to include an explicit language token such as text, jql, or markdown
(e.g., ```text, ```jql, ```markdown). Search for bare ``` blocks in the SKILL.md
content and add the appropriate language label to each fence so all examples
satisfy MD040 while keeping the fence content unchanged.
---
Duplicate comments:
In @.cursor/skills/summarize-issues/SKILL.md:
- Line 1: The summarize-issues skill (SKILL.md) is in the global .cursor skills
tree but must live under a plugin's skills tree; move the "summarize-issues"
SKILL.md into the target plugin’s skills directory by creating a new folder for
the skill under that plugin’s skills area (e.g., <plugin>-skills/your-skill/),
place SKILL.md there, and update any references or exports that point to
".cursor/skills/summarize-issues/SKILL.md" so they reference the new
plugin-scoped location; ensure the skill directory name remains
"summarize-issues" and metadata in SKILL.md (if any) is unchanged.
In @.cursor/skills/summarize-pr-reviews/SKILL.md:
- Line 1: The SKILL.md for the "summarize-pr-reviews" skill is placed under
.cursor/skills which breaks plugin discovery; move the skill into your plugin's
skills directory by creating plugins/<plugin-name>/skills/summarize-pr-reviews/
and relocating SKILL.md there (and update any internal references or imports to
point to the new location) so the skill follows the plugins/*/skills/**
discovery pattern.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 7f673561-701d-4808-89ac-e32742955e2f
📒 Files selected for processing (2)
.cursor/skills/summarize-issues/SKILL.md.cursor/skills/summarize-pr-reviews/SKILL.md
|
|
||
| First, get the user's Atlassian account info and accessible resources. | ||
|
|
||
| ``` |
There was a problem hiding this comment.
Specify languages for fenced code blocks (MD040).
Add fence labels (text, jql, etc.) to satisfy markdownlint and improve readability.
Also applies to: 34-34, 45-45, 60-60, 82-82
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 22-22: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.cursor/skills/summarize-issues/SKILL.md at line 22, Several fenced code
blocks in SKILL.md lack language labels causing MD040 failures; add appropriate
fence labels (e.g., text, jql, json, bash) immediately after each opening ```
for the blocks referenced (lines noted in the review: 22, 34, 45, 60, 82) so
markdownlint recognizes the language and improves readability—edit each ``` to
```text or ```jql (or another suitable language) depending on the block content.
| "Contributor[User Picker (multiple users)]" = currentUser() AND updated >= -3d | ||
| ``` | ||
|
|
||
| **High priority backlog (not in sprint):** |
There was a problem hiding this comment.
Use hyphenation for the compound adjective.
Change “High priority backlog” to “High-priority backlog”.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~235-~235: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...currentUser() AND updated >= -3d **High priority backlog (not in sprint):**jql assig...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.cursor/skills/summarize-issues/SKILL.md at line 235, Replace the phrase
"High priority backlog" with the hyphenated compound adjective "High-priority
backlog" in the document; locate the exact occurrence shown in the diff (the
line containing **High priority backlog (not in sprint):**) and update it to
**High-priority backlog (not in sprint):** to correct hyphenation.
|
|
||
| First, get the authenticated GitHub user's information. | ||
|
|
||
| ``` |
There was a problem hiding this comment.
Add language identifiers to fenced code blocks.
markdownlint MD040 is triggered repeatedly; add explicit languages (e.g., text, jql, or markdown) to these fences.
Also applies to: 32-32, 42-42, 52-52, 66-66, 75-75, 84-84, 262-262, 267-267, 272-272, 277-277, 282-282, 287-287
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 21-21: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.cursor/skills/summarize-pr-reviews/SKILL.md at line 21, Multiple fenced
code blocks in SKILL.md trigger markdownlint MD040 because they lack language
identifiers; update each triple-backtick fence (``` ) used throughout the
document — including the occurrences noted around the examples — to include an
explicit language token such as text, jql, or markdown (e.g., ```text, ```jql,
```markdown). Search for bare ``` blocks in the SKILL.md content and add the
appropriate language label to each fence so all examples satisfy MD040 while
keeping the fence content unchanged.
2 participants
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.
Summary by CodeRabbit
New Features