بنقرة واحدة
prds-get
Fetch all open GitHub issues — PRDs and standalone issues — for project planning
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Fetch all open GitHub issues — PRDs and standalone issues — for project planning
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Draft, polish, and create a well-formed GitHub issue with required structure
Post a structured checkpoint comment to the relevant issue and commit current code state
Close out issue work - ensure PR exists, run the full CodeRabbit + /code-review gate, merge, close all issues in the working set, clean branches, and update PROGRESS.md
Fresh session pickup using the most recent checkpoint comment and git log — reconstructs working context for active issue work
Recommend juggling pairs, user decides, create correctly-named branch for issue work
Update the active issue with a design decision and cascade impact to all open issues and PRDs
| name | prds-get |
| description | Fetch all open GitHub issues — PRDs and standalone issues — for project planning |
| category | project-management |
Fetch all open GitHub issues from this project: PRDs (labeled PRD) and standalone issues (everything else). Present both in a single overview for project planning.
Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
Fetch all open issues in a single call:
gh issue list --state open --json number,title,url,labels,body,createdAt,updatedAt
Split the results into two groups:
PRDPresent PRDs as a table:
git branch --show-current). If it matches feature/prd-<number>-*, mark that PRD as (active) in the table.Present standalone issues as a separate table:
Dependency and blocking analysis across both groups:
Next steps suggestion based on the full picture: