boring-feedback

Automating GitHub issue creation from agent session data involves capturing system state, error logs, and user context to generate standardized, context-aware bug reports for efficient tracking and triage. This skill enforces strict labeling and redaction policies to ensure secure documentation.

The best way to report agent errors with full context is to use an automated feedback process that captures session metadata, branch information, and redacted error logs, enforcing a consistent issue format and labeling strategy for actionable bug tracking.

Standardized GitHub issue formatting improves agent bug tracking by enforcing consistent structure and labeling, ensuring all feedback is categorized correctly and developers receive the necessary session and error context to reproduce and resolve issues efficiently.

Yes, you need a GitHub API integration and session management tools to automate issue reporting from your agent workflow. These dependencies ensure secure and consistent issue documentation by connecting the agent environment directly to your repository.

Yes, error logs are redacted when creating automated GitHub issues from agent sessions. The automated reporting process enforces strict redaction policies to ensure secure and consistent issue documentation while capturing necessary system state and user context.

To trigger automated feedback generation for an unexpected agent error, type the /feedback command during your active session to instantly capture the current session state and generate a new GitHub issue with relevant error context and a proposed resolution plan.