Skip to content

[aw] Add Community Extension from Issue Submission failed #3041

@github-actions

Description

@github-actions

Workflow Failure

Workflow: Add Community Extension from Issue Submission
Branch: main
Run: https://github.com/github/spec-kit/actions/runs/27723132812
Pull Request: #2884

⚠️ Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

  1. GitHub MCP tool github-issue_read: Failed with integrity policy filter - "Resource 'issue:[Bug]: get_feature_paths persists .specify/feature.json during read-only path resolution (check-prerequisites.sh --paths-only) #3025' has lower integrity than agent requires. The agent cannot read data with integrity below 'approved'."
  2. GitHub CLI via bash: Failed - gh is not authenticated (missing GH_TOKEN environment variable)

The workflow requires reading the issue body to extract extension metadata fields (extension-id, extension-name, version, description, author, repository, download-url, license, etc.) from the GitHub issue form format. Without access to the issue content, validation and catalog entry creation cannot proceed.

This appears to be an infrastructure/authentication configuration issue rather than a logic error in the workflow.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/spec-kit/actions/runs/27723132812
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Add Community Extension from Issue Submission · sonnet45 276.3K ·

  • expires on Jun 24, 2026, 10:17 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions