Skip to content

docs(prompt-library): add github-issue-labeler intermediate prompt - #5002

Closed
Mohammed-Thaha wants to merge 3 commits into
aaif-goose:mainfrom
Mohammed-Thaha:prompt/github-issue-labeler
Closed

docs(prompt-library): add github-issue-labeler intermediate prompt#5002
Mohammed-Thaha wants to merge 3 commits into
aaif-goose:mainfrom
Mohammed-Thaha:prompt/github-issue-labeler

Conversation

@Mohammed-Thaha

@Mohammed-Thaha Mohammed-Thaha commented Oct 3, 2025

Copy link
Copy Markdown
Contributor

Summary

Added intermediate prompt "GitHub Issue Labeler" to the Prompt Library. This prompt uses exactly 2 extensions (GitHub MCP server + Developer builtin) to analyze GitHub issues and suggest labels, triage comments, priority levels, and recommended assignees in structured JSON format. The prompt demonstrates integration between the GitHub MCP server for fetching issue data and the Developer extension for local analysis and JSON formatting.

Type of Change

  • Documentation

Testing

Manual validation completed:

  • Verified JSON syntax using python3 -c "import json; json.load(open('github-issue-labeler.json'))"
  • Confirmed all required fields present: id, title, description, category, example_prompt, example_result, extensions
  • Validated exactly 2 extensions:
    • GitHub MCP server: npx -y @modelcontextprotocol/server-github
    • Developer builtin extension: developer
  • Verified filename matches title: github-issue-labeler.json → "GitHub Issue Labeler"
  • Confirmed environment variables documented (GITHUB_PERSONAL_ACCESS_TOKEN required)
  • Built and tested goose CLI locally: cargo build -p goose-cli && ./target/debug/goose --help
  • Verified file structure follows existing prompt library patterns
  • Checked integration demonstrates GitHub data fetching + Developer processing

Submission checklist verification:

  • ✅ Unique and descriptive filename
  • ✅ Title matches filename exactly
  • ✅ JSON includes all required fields
  • ✅ Uses exactly 2 extensions (requirement met)
  • ✅ Local testing completed

Related Issues

Relates to #4997
Discussion: N/A

Screenshots/Demos (for UX changes)

Before: N/A
After: N/A

Email: mohammedthahacse@gmail.com

@Mohammed-Thaha
Mohammed-Thaha requested a review from a team as a code owner October 3, 2025 23:07
@EbonyLouis

Copy link
Copy Markdown
Contributor

Hey @Mohammed-Thaha thank you for contributing. The DCO check is failing, this link will tell you how to fix it.

Thanks

Signed-off-by: mohammed-thaha <mohammedthahacse@gmail.com>
@Mohammed-Thaha

Mohammed-Thaha commented Oct 7, 2025

Copy link
Copy Markdown
Contributor Author

Hi @EbonyLouis

Thanks for the feedback,
I have fixed the DCO sign-off issue and force-pushed the updated commit.
The DCO check should now pass.

Ready for review!

Thank you

- Replace broken link with official GitHub MCP server repository
- Ensure extension documentation is accessible to users

Signed-off-by: mohammed-thaha <mohammedthahacse@gmail.com>
Comment thread documentation/src/pages/prompt-library/data/prompts/github-issue-labeler.json Outdated
Comment thread documentation/src/pages/prompt-library/data/prompts/github-issue-labeler.json Outdated
- Validates JSON structure and output format
- Verifies GitHub API accessibility for target issue
- Tests extension integration (GitHub MCP + Developer)
- Provides copy-paste ready automation for issue triage
- Meets all intermediate prompt requirements (2 extensions, structured output)

Signed-off-by: mohammed-thaha <mohammedthahacse@gmail.com>
@Mohammed-Thaha Mohammed-Thaha closed this by deleting the head repository Oct 20, 2025
@taniacryptid

Copy link
Copy Markdown
Collaborator

Was there a reason you closed this? o: @Mohammed-Thaha

@Mohammed-Thaha

Copy link
Copy Markdown
Contributor Author

hey @taniandjerry thanks for asking
i didn’t mean to close it my fork got deleted accidentally, which automatically closed the PR.
i will recreate the fork and open a new pull request soon.

@taniacryptid

Copy link
Copy Markdown
Collaborator

Thank you for letting me know. Please make sure to link it to the appropriate issue (not issue hub) when you have it ready. @Mohammed-Thaha

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.

4 participants