gh-pr-auto-detector
Auto-detection: when user mentions GitHub PRs (URLs, #123, owner/repo#123, 'PR #123') and needs context (asking questions, checking CI status, comparing, applying changes), automatically fetches condensed PR summary via gh-pr-reviewer subagent. Skips auto-fetch for past tense mentions, passive listings, technical identifiers, or already-fetched PRs.
What this skill does
# GitHub PR Auto-Detector Skill
Seamlessly integrates GitHub PR context into conversations without polluting the main context window. You decide WHEN to fetch; the gh-pr-reviewer subagent decides HOW to fetch and what to condense.
For explicit review requests ("review #123", `/schovi:review`), the `review` skill owns the whole flow. Don't activate on top of it.
## Codex Compatibility
If a Claude-style `Task` tool or custom `subagent_type` is unavailable, use the `gh` CLI commands described in `plugins/schovi/agents/gh-pr-reviewer/AGENT.md` directly, then condense the result. Never paste raw PR payloads.
## Pattern Recognition
- **Full URL**: `https://github.com/owner/repo/pull/123`
- **Short form**: `owner/repo#123`
- **Hash-only**: `#123`
- **Explicit**: "PR #123", "pull request 123"
**Repository resolution for bare `#123`:**
1. Check conversation history for previous repo context
2. Check cwd: `git remote get-url origin`, parse owner/repo
3. If neither works, ask user to clarify
## When to Fetch
- Questions about a PR: "What is #123 about?", "What's in owner/repo#456?"
- Status checks: "Did CI pass on #123?", "Is #456 approved?"
- Context needs: "Apply changes from #123", "Why did #123 fail?"
- Comparisons: "Compare #123 and #456"
## When to Skip
- Past tense: "I merged #123 yesterday", "Fixed in #456"
- Passive listing: "Released with #123, #124, #125"
- Technical identifier: "The PR-123 endpoint", "Variable pr_456_result"
- Already fetched this session (check transcript for previous gh-pr-reviewer calls)
## Workflow
### Step 1: Detect & Evaluate
Scan the message for PR patterns. For each match, apply the fetch/skip rules above.
### Step 2: Fetch
```
Tool: Task
Parameters:
subagent_type: "schovi:gh-pr-reviewer:gh-pr-reviewer"
prompt: "Fetch and summarize GitHub PR: [owner/repo#number or URL]"
description: "Fetching GitHub PR context"
```
### Step 3: Integrate Naturally
Answer the user's question using the relevant parts of the summary. Don't regurgitate the full summary.
**Multiple PRs:** Fetch max 3 per response. Launch in parallel when independent.
## Session Memory
Track what you've fetched this conversation. Reuse existing context; re-fetch only if the user explicitly requests fresh data or needs different aspects.
## Error Handling
- **PR not found**: Report error, suggest checking PR number and repository
- **Auth failure**: Suggest `gh auth login`
- **Missing repo context**: Ask user to specify as `owner/repo#123`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.