Skip to content
This repository was archived by the owner on Jul 11, 2026. It is now read-only.
This repository was archived by the owner on Jul 11, 2026. It is now read-only.

[CI/CD Layer] Build & Pipeline Awareness Service #16

Closed
Closed
[CI/CD Layer] Build & Pipeline Awareness Service#16
Labels
enhancementNew feature or requestlayer:analysisAnalysis Layer - static analysis & impactpriority:highHigh priority item

Description

@gloomcheng
gloomcheng
opened on Dec 25, 2025

Problem

Claude Code doesn't know:

  • Current build status (passing/failing)
  • Which tests are failing in CI
  • Deployment pipeline status
  • Previous build failures on similar changes

Developer Pain Points

  • AI suggested a change that failed CI
  • No learning from previous CI failures
  • Have to manually check GitHub Actions
  • Same test keeps failing but no visibility

Proposed Solution

CI/CD Integration Service that:

  1. Reads GitHub Actions workflow status
  2. Parses test failure logs
  3. Tracks build history
  4. Pre-validates changes against past failures

Features

  • GitHub Actions integration via gh CLI
  • Test failure log parsing
  • Build history tracking
  • Failure pattern detection

MCP Tools

  • ci-status: Get current build status
  • ci-failures: Show failing tests
  • ci-history: Build history for files
  • ci-validate: Pre-validate changes

Priority

Critical - Prevents broken builds

Effort Estimate

2 days

Activity

  1. gloomcheng
    added
    enhancementNew feature or request
    priority:highHigh priority item
    layer:analysisAnalysis Layer - static analysis & impact
    on Dec 25, 2025

  2. gloomcheng commented on Dec 25, 2025

    @gloomcheng
    gloomcheng
    on Dec 25, 2025
    ContributorAuthor

    Completed in commit dcea749.

    Implementation Summary

    CIPipelineService (614 lines)

    GitHub Actions integration via gh CLI:

    • getStatus() - Get current build status and workflow runs
    • getFailures() - Parse test failures from CI logs
    • getHistory() - Track build history for specific files
    • validateChanges() - Pre-validate changes against failure patterns

    MCP Tools (4 tools)

    • ci-status - Current build status (success rate, failing workflows)
    • ci-failures - Failing tests with error messages and stack traces
    • ci-history - Build history for specific files
    • ci-validate - Pre-validate changes based on CI failure history

    Features

    • GitHub Actions integration via gh CLI
    • Test failure log parsing (Jest format)
    • Build history tracking (stored in .cortex/ci-history.json)
    • Failure pattern detection (.cortex/ci-failure-patterns.json)
    • Risk assessment for file changes (low/medium/high)

    Acceptance Criteria

    • GitHub Actions integration via gh CLI
    • Test failure log parsing
    • Build history tracking
    • Failure pattern detection
    • 4 MCP tools registered
    • Build passing
  3. gloomcheng
    closed this as completedon Dec 25, 2025
  4. gloomcheng
    added a commit that references this issue on Dec 25, 2025

    feat: implement CI/CD build & pipeline awareness service (Issue #16)

    dcea749
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestlayer:analysisAnalysis Layer - static analysis & impactpriority:highHigh priority item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions