context-collector

To collect context for GitHub issues automatically, this Skill fetches issue details, briefs, QA reports, and branch histories via the GitHub API. It outputs a structured .md file to the .agent-output/context directory for documentation and collaboration.

Automated GitHub issue context collection gathers related briefs, QA reports, and branch histories into a structured .md file. You need this when preparing for issue discussions or updating issue documentation to reduce manual errors and save time.

Yes, you need GitHub API access to gather issue documentation and branch histories. The context collection process requires this access to automatically fetch issue details and write the collected data into structured .md context files.

The best way to prepare structured context files for issue collaboration is to automate the collection of GitHub issues, briefs, and QA reports. This generates a structured .md file, ensuring all relevant context is organized for team consumption.

Yes, context collection for GitHub issues works with branch histories and QA reports. It automatically collects data from these sources alongside issue details, compiling them into a single structured .md file for documentation.

GitHub issue context collection writes specifically to the .agent-output/context directories. If your context collection is not working, ensure your environment has proper GitHub API access and the script can create or write to the .agent-output/context path.