Menu
Knowledge on how to work with Github projects. To be used when asked to "create a task in github project" or "add ticket to gh project" or similar.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
This skill should be used when the user asks to "update the PR", "update PR body", "update PR title", "sync PR description", "update pull request", or wants the pull request title and body to reflect the actual changes on the current branch.
Use when the user asks to implement a feature, add functionality, or build something new.
This skill should be used when the user asks to "open a browser", "navigate to a URL", "test the UI", "check a page", "browse a website", "take a screenshot", "fill a form", "click a button", or any browser automation task. Also triggered by CLAUDE.md directives like "Use 'agent-browser' when navigating".
FastAPI engineering choices. To be used when asked to "create router", "create crud router", "add new endpoint" or similar in a fastapi codebase.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
This skill should be used when the user asks to "investigate something incrementally", "start a discovery journal", "journal my findings", "explore this step by step and write it down", "create a research journal", or wants to build understanding of a problem through guided, step-by-step investigation with findings persisted to a journal file.
| name | github-projects |
| description | Knowledge on how to work with Github projects. To be used when asked to "create a task in github project" or "add ticket to gh project" or similar. |
<OWNER>) and project number (<PROJECT_NUMBER>).skills/github-projects/scripts/.gh commands with escalation (sandbox_permissions: "require_escalated").gh command works in sandbox, escalation is still preferred for consistency.gh session.gh is configured correctly.skills/github-projects/scripts/create_backlog_item.sh \
--owner <OWNER> \
--project <PROJECT_NUMBER> \
--title "<TITLE>" \
--body "<BODY>"
Optional status overrides:
skills/github-projects/scripts/create_backlog_item.sh \
--owner <OWNER> \
--project <PROJECT_NUMBER> \
--title "<TITLE>" \
--body "<BODY>" \
--status-field "Status" \
--status-option "Backlog"
Use when a draft task is ready to become implementation work in a repo.
skills/github-projects/scripts/promote_draft_to_issue.sh \
--owner <OWNER> \
--project <PROJECT_NUMBER> \
--item-id <DRAFT_ITEM_ID> \
--repo <OWNER/REPO>
Optional flags:
--status-option "<OPTION>" (also supports --status-field)--labels "bug,help wanted"--assignees "@me,octocat"--keep-draft (default is archive draft)--title-override "<TITLE>"--body-file /tmp/spec.md--dry-runUse this when the draft is a quick todo and the real issue is written later with full context.
title + body).promote_draft_to_issue.sh with final title/body (prefer --body-file for long specs).Gather these before creating the issue:
Only create/link the issue when:
gh project ... commands out of responses unless explicitly requested.Tickets contain little information, they precede an issue linked to them that contain all the implementation information.