القائمة
Use when /internal-github routes pull-request lifecycle work covering creation, body updates, readiness, reviews, merge, or terminal-state verification.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when creating, reviewing, or materially revising a repository-owned Copilot agent under `.github/agents/`.
Use when /internal-aws selects the AWS governance lane for IAM operating models, trust policies, federation, permission boundaries, SCPs, tag policies, exception controls, or access guardrails.
Use when /internal-aws selects the AWS Lambda lane for handlers, event sources, runtimes, packaging, retries, concurrency, cold starts, or Lambda-specific configuration.
Use when /internal-aws selects the AWS research lane to retrieve current official AWS documentation, regional availability, service behavior, IAM state, or policy-simulation evidence.
Use when /internal-aws selects the AWS operations lane for monitoring, logging, rollout validation, backup and restore proof, DR evidence, reporting, or audit evidence.
| name | internal-github-pr |
| description | Use when /internal-github routes pull-request lifecycle work covering creation, body updates, readiness, reviews, merge, or terminal-state verification. |
| user-invocable | false |
Own pull-request lifecycle work from template resolution through verified terminal state. Ground every statement in the actual diff, review state, and fresh validation evidence.
Use when the requested deliverable is pull-request content, review readiness, merge execution, or repository-scoped terminal-state proof.
gh pr merge --squash unless the repository standardizes another
allowed method. Use --admin only when policy permits a bypass.gh pr view --json state,mergedAt and verify the final PR state.Check these paths in order and use the first existing template:
.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE.mdpull_request_template.mdKeep headings and section order unchanged. Mark an inapplicable section N/A.