القائمة
Use when integrating GitHub Projects. Trigger with GitHub sync, label setup, or PR workflow requests.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/tomevault-io/skills-registry --skill eia-github-integrationيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | eia-github-integration |
| description | Use when integrating GitHub Projects. Trigger with GitHub sync, label setup, or PR workflow requests. |
| license | Apache-2.0 |
| compatibility | Requires GitHub CLI version 2.14 or higher, GitHub account with write permissions to target repositories, and basic Git knowledge. Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| agent | api-coordinator |
| context | fork |
| workflow-instruction | support |
| procedure | support-skill |
| user-invocable | false |
This skill is the entry point for all GitHub integration tasks in agent orchestration workflows. It routes you to specialized skills based on your task type. Use this skill to determine which specialized GitHub skill to invoke.
Before using any GitHub integration skill, ensure:
gh --version)gh auth status)First-time setup:
# Install GitHub CLI
brew install gh # macOS
# or see https://cli.github.com/manual/installation for other platforms
# Authenticate
gh auth login
# Verify authentication
gh auth status
For detailed setup instructions, see references/prerequisites-and-setup.md.
Use this decision tree to route to the appropriate specialized skill:
→ Use eia-github-pr-workflow
This skill covers:
→ Use eia-github-projects-sync
This skill covers:
→ Use eia-kanban-orchestration
This skill covers:
→ Use eia-git-worktree-operations
This skill covers:
This reference covers:
This reference covers:
gh_multiuser.py script for automated identity managementWhen you need to perform operations that span multiple GitHub areas (e.g., bulk label changes across issues AND PRs, or cross-project synchronization):
Reference: references/batch-operations.md
Use when:
Quick example:
# Bulk add label to all open issues with "feature" label
gh issue list --label "feature" --state open --json number --jq '.[].number' | \
xargs -I {} gh issue edit {} --add-label "priority:high"
Reference: references/automation-scripts.md
Use when:
sync-projects-v2.py)bulk-label-assignment.py)monitor-pull-requests.py)bulk-create-issues.py)generate-project-report.py)gh --version in your terminal.gh auth status. If not authenticated, run gh auth login and follow the prompts.eia-github-pr-workflow for PR tasks).gh issue list or gh pr list before executing changes.gh issue view <number>, gh pr status).Copy this checklist and track your progress:
gh --versiongh auth statusgh issue list or gh pr list)gh issue view, gh pr status)This skill produces the following outputs depending on the operation performed:
eia-github-pr-workflow, eia-github-projects-sync).generate-project-report.py produces a Markdown status report).gh CLI commands showing the current state of issues, PRs, or project boards after modifications.| Error | Cause | Resolution |
|---|---|---|
gh: command not found | GitHub CLI is not installed or not in PATH | Install with brew install gh (macOS) or see references/prerequisites-and-setup.md |
HTTP 401 - Bad credentials | Authentication token expired or revoked | Re-authenticate with gh auth login and verify with gh auth status |
HTTP 403 - Resource not accessible | Insufficient permissions on the target repository | Request write access from the repository owner, or check that your token has the required scopes (repo, project) |
HTTP 422 - Validation Failed | Invalid field values (e.g., non-existent label name, malformed project field) | Verify the label exists with gh label list or check project field names with gh project field-list |
API rate limit exceeded | Too many API calls in a short period | Wait for the rate limit reset (check gh api rate-limit), or use GraphQL to batch multiple queries into one request |
Could not resolve to a Project | Wrong project number or the project is in a different organization | Verify the project number with gh project list --owner <org> and ensure you are targeting the correct owner |
xargs: gh: terminated by signal 13 | Pipe broken during batch operation, often due to API errors mid-stream | Re-run the batch operation with smaller batch sizes or add error handling with `xargs -I {} sh -c 'gh issue edit {} --add-label "label" |
Example 1: Route to the correct skill for a PR task
You receive a request: "Create a PR for the feature branch and link it to issue #42."
This is a Pull Request task. According to the decision tree, invoke eia-github-pr-workflow:
# Switch to eia-github-pr-workflow skill, then run:
gh pr create --base main --head feature-branch --title "Implement feature X" \
--body "Closes #42" --assignee "@me"
Example 2: Bulk add a label to all open bug issues
You need to add the priority:critical label to all issues labeled bug that are currently open:
# Step 1: Preview affected issues (dry-run)
gh issue list --label "bug" --state open --json number,title --jq '.[] | "\(.number): \(.title)"'
# Step 2: Apply the label change
gh issue list --label "bug" --state open --json number --jq '.[].number' | \
xargs -I {} gh issue edit {} --add-label "priority:critical"
# Step 3: Verify a sample issue
gh issue view 15 --json labels --jq '.labels[].name'
Example 3: Check which skill to use for a Projects V2 sync request
You receive a request: "Sync the agent task board with the GitHub Project for repository X."
This is a GitHub Projects V2 synchronization task. According to the decision tree, invoke eia-github-projects-sync:
# Verify the project exists first
gh project list --owner Emasoft --format json
# Then follow the eia-github-projects-sync skill instructions for bidirectional sync
uv run python scripts/sync-projects-v2.py --repo Emasoft/repo-x --project 3 --direction bidirectional
If you encounter issues with any GitHub integration task, see references/troubleshooting.md for:
Core References:
Specialized Skills:
eia-github-pr-workflow - Pull request operationseia-github-projects-sync - Projects V2 bidirectional synchronizationeia-kanban-orchestration - Kanban board and 9-label system managementeia-git-worktree-operations - Git worktree managementSkill Version: 2.0.0 Last Updated: 2026-02-05 Maintainer: Skill Development Team Changelog:
gh_multiuser.py script with configuration-driven identity managementConverted and distributed by TomeVault — claim your Tome and manage your conversions.