You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This security policy is designed to protect against:
Prompt injection in issue bodies
Malicious URLs or content in submissions
Untrusted data that could influence agent behavior
To process this submission safely, one of the following is needed:
Manual review and approval of the issue content to raise its integrity level
A different agent configuration that can handle lower-integrity input with appropriate sanitization
A human reviewer to extract and validate the submission data before passing to the agent
The workflow cannot proceed automatically with the current security constraints.
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/27720902873
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: Add Community Preset from Issue Submission
Branch: main
Run: https://github.com/github/spec-kit/actions/runs/27720902873
Pull Request: #2884
Reasons:
Cannot access issue [Bug]: get_feature_paths emits empty CURRENT_BRANCH when SPECIFY_FEATURE unset, despite feature context via SPECIFY_FEATURE_DIRECTORY/feature.json #3026 due to integrity policy restrictions. The issue content is filtered because it has lower integrity than this agent requires. This prevents processing untrusted community submissions that could contain malicious content or prompt injection attempts.
The GitHub MCP server returned: "issue:[Bug]: get_feature_paths emits empty CURRENT_BRANCH when SPECIFY_FEATURE unset, despite feature context via SPECIFY_FEATURE_DIRECTORY/feature.json #3026 exists but is not accessible — filtered by integrity policy (Resource 'issue:[Bug]: get_feature_paths emits empty CURRENT_BRANCH when SPECIFY_FEATURE unset, despite feature context via SPECIFY_FEATURE_DIRECTORY/feature.json #3026' has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)"
This security policy is designed to protect against:
To process this submission safely, one of the following is needed:
The workflow cannot proceed automatically with the current security constraints.
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.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow add-community-preset failure in https://github.com/github/spec-kit/actions/runs/27720902873Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: