/context-load-github-actions

allowed-tools: WebFetch, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, Read, Bash(fd:*), Bash(rg:*), Bash(yq:*), Bash(gdate:*), Bash(git:*), Bash(wc:*)
name: "Context Load Github Actions"
description: "Load comprehensive GitHub Actions CI/CD documentation with adaptive project-specific context and modern workflow patterns"
author: "wcygan"
tags: ["context","web"]
version: "1.0.0"
created_at: "2025-07-14T00:00:00Z"
updated_at: "2025-07-14T00:00:00Z"

Context

• Session ID: !`gdate +%s%N`
• Current directory: !`pwd`
• Project type detection: !`fd "(package\.json|Cargo\.toml|go\.mod|pom\.xml|deno\.json|requirements\.txt|composer\.json|build\.gradle)$" . -d 2 | head -5 || echo "No config files detected"`
• GitHub workflows directory: !`fd "\.github" . -t d -d 3 || echo "No .github directory found"`
• Existing workflows: !`fd "\.(yml|yaml)$" .github/workflows -t f 2>/dev/null | wc -l | tr -d ' ' || echo "0"`
• Workflow patterns: !`rg "(runs-on|uses:|with:)" .github/workflows/ --type yaml -c 2>/dev/null | head -3 || echo "No workflow patterns detected"`
• Repository context: !`git remote get-url origin 2>/dev/null | sed 's/.*github\.com[:/]\([^/]*\/[^/]*\)\.git.*/\1/' || echo "No GitHub remote detected"`
• Technology indicators: !`rg "(cargo|npm|go|maven|gradle|deno)" . --type json --type toml --type yaml -i | head -5 | cut -d: -f3 | sort -u || echo "Technology stack unknown"`
• Container usage: !`fd "(Dockerfile|docker-compose)" . -t f -d 2 || echo "No container files detected"`
• Test frameworks: !`rg "(test|spec)" . --type json --type toml --type yaml | head -3 | cut -d: -f1 | sort -u || echo "No test patterns detected"`

Your Task

STEP 1: Initialize adaptive GitHub Actions context loading session

• CREATE session state file: `/tmp/github-actions-context-$SESSION_ID.json`
• SET initial state:

  {
    "sessionId": "$SESSION_ID",
    "timestamp": "$(gdate -Iseconds 2>/dev/null || date -Iseconds)",
    "project_type": "auto-detect",
    "existing_workflows": 0,
    "technology_stack": [],
    "context_loaded": {
      "core_docs": false,
      "security_guides": false,
      "technology_specific": false,
      "marketplace_actions": false,
      "advanced_patterns": false
    },
    "focus_areas": [],
    "custom_recommendations": []
  }

STEP 2: Analyze project characteristics and determine context loading strategy

• ANALYZE project structure from Context section
• DETECT primary technology stack and frameworks
• IDENTIFY existing GitHub Actions workflows and patterns
• ASSESS CI/CD complexity requirements based on project characteristics

IF existing_workflows > 0:

• SET focus = "enhancement_and_optimization"
• PRIORITIZE advanced patterns, security hardening, performance optimization

ELSE IF technology_stack detected:

• SET focus = "technology_specific_implementation"
• PRIORITIZE technology-specific CI/CD patterns and best practices

ELSE:

• SET focus = "foundational_setup"
• PRIORITIZE basic workflow creation, common patterns, getting started guides

STEP 3: Load core GitHub Actions documentation using adaptive strategy

TRY:

• USE Context7 MCP server to load comprehensive GitHub Actions documentation:
• RESOLVE library ID for GitHub Actions documentation
• LOAD core workflow syntax and configuration patterns
• FOCUS on: workflow triggers, jobs, steps, expressions, contexts

IF Context7 unavailable:

• FALLBACK to WebFetch for essential documentation:
• **Core GitHub Actions**: `https://docs.github.com/en/actions`
• **Workflow Syntax**: `https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions`
• **Events and Triggers**: `https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows`

• UPDATE state: context_loaded.core_docs = true

STEP 4: Load technology-specific CI/CD patterns and marketplace actions

CASE detected_technology: WHEN "rust" OR "cargo":

• LOAD Rust-specific GitHub Actions patterns:
• Cargo caching strategies and optimization
• Cross-compilation workflows and target matrices
• Security auditing with cargo-audit and cargo-deny
• Documentation generation and publishing
• Performance benchmarking in CI
• FETCH popular Rust actions from marketplace:
• actions/cache for Cargo dependencies
• actions-rs/toolchain for Rust toolchain management
• actions-rs/cargo for Cargo command execution

WHEN "go" OR "golang":

• LOAD Go-specific CI/CD patterns:
• Go module caching and dependency management
• Multi-version testing matrices
• Cross-platform building with GOOS/GOARCH
• Integration testing with services
• Code coverage reporting and analysis
• FETCH Go-specific marketplace actions:
• actions/setup-go for Go environment setup
• golangci/golangci-lint-action for linting

WHEN "java" OR "maven" OR "gradle":

• LOAD Java ecosystem CI/CD patterns:
• Maven/Gradle dependency caching
• Multi-JDK testing strategies
• Spring Boot application deployment
• Container image building and publishing
• Enterprise integration testing patterns
• FETCH Java-specific marketplace actions:
• actions/setup-java for JDK setup
• gradle/gradle-build-action for Gradle builds

WHEN "typescript" OR "javascript" OR "node" OR "npm" OR "deno":

• LOAD JavaScript/TypeScript CI/CD patterns:
• Node.js dependency caching (npm, yarn, pnpm)
• Multi-Node version testing matrices
• Frontend build optimization and deployment
• Package publishing to npm registry
• End-to-end testing with Playwright/Cypress
• FETCH Node.js-specific marketplace actions:
• actions/setup-node for Node.js environment
• pnpm/action-setup for pnpm package manager

WHEN "python":

• LOAD Python-specific CI/CD patterns:
• Python dependency caching with pip/poetry
• Multi-Python version testing
• Virtual environment management
• Package publishing to PyPI
• Data science and ML workflow patterns
• FETCH Python-specific marketplace actions:
• actions/setup-python