file-issues

Parse evaluation reports and file GitHub issues for each identified shortcoming.

11|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/brazil-bench/pourpoise --skill file-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-issues
Source: https://github.com/brazil-bench/pourpoise/tree/main/skills/file-issues
Command: npx skills add https://github.com/brazil-bench/pourpoise --skill file-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill parses evaluation reports from brazil-bench reviews and automatically creates GitHub issues on each attempt repository for every shortcoming, warning, or improvement identified during the review process.

Core Features & Use Cases

  • Automated issue creation: Generates one issue per identified shortcoming, warning, or improvement and links it back to the evaluation report.
  • Cross-repo applicability: Works with Python and Swift/iOS projects and supports standard brazil-bench review workflows.
  • Traceability: Keeps a record of filed issues and maps them to the exact evaluation artifact (results/{attempt_repo}.md) for auditability.

Quick Start

Run the filing process against a provided evaluation report, e.g., results/2025-12-13-python-claude-hive.md, to create detailed issues in the corresponding attempt repository.

Frequently Asked Questions about file-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create GitHub issues from markdown evaluation reports?

To automatically create GitHub issues from markdown evaluation reports, you parse the review findings and use the GitHub API to generate one structured issue per identified shortcoming or improvement on the corresponding attempt repository.

Can I file GitHub issues automatically for both Python and Swift iOS projects?

Yes, you can file GitHub issues automatically for both Python and Swift iOS projects. The parsing workflow targets standard review workflows and operates across both project types to generate issues from markdown evaluation outputs.

Do I need GitHub API access to parse evaluation reports and file issues?

Yes, you need GitHub API access to file issues parsed from evaluation reports. The process requires API authentication to read markdown evaluation outputs and automatically create structured issue bodies on each attempt repository.

What is the best way to track evaluation shortcomings as traceable GitHub issues?

The best way to track evaluation shortcomings as traceable GitHub issues is to parse markdown review reports and map each filed issue back to the exact evaluation artifact, ensuring full auditability for every identified warning or improvement.

How does automated issue generation handle default labels during GitHub issue filing?

Automated issue generation uses the default labels available on the target attempt repository when filing parsed evaluation findings. It reads the markdown evaluation outputs and applies these standard labels to the structured issue bodies.