report

Report steer plugin defects via GitHub after deduplication and secrets scrubbing.

2|Updated May 19, 2026
One-click install
npx skills add https://github.com/element22llc/e22-plugins --skill report-element22llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/element22llc/e22-plugins/tree/main/plugins/steer/skills/report
Command: npx skills add https://github.com/element22llc/e22-plugins --skill report-element22llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, mcp__github__*, git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reporting defects in the steer plugin itself, streamlining the bug reporting process and ensuring issues are filed correctly and efficiently.

Core Features & Use Cases

  • Automated Bug Reporting: Quickly report defects in the steer plugin directly upstream.
  • Secrets Scrubbing: Automatically scrubs sensitive information before reporting.
  • Deduplication: Prevents duplicate bug reports.
  • Use Case: When a user encounters a malfunction in the steer plugin, they can use this Skill to automatically generate and file a bug report, saving time and ensuring the issue is addressed promptly.

Quick Start

Report a bug in the steer plugin by running: /steer:report [describe the defect]

Frequently Asked Questions about report

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

FAQPage Schema
How do I automatically report bugs in the steer plugin to GitHub?

To automatically report bugs in the steer plugin, run the command `/steer:report [describe the defect]` to scrub sensitive data, dedupe against existing issues, and file the report upstream via GitHub.

Does automated bug reporting scrub sensitive information before creating a GitHub issue?

Yes, automated bug reporting scrubs sensitive information from the defect description before deduping and filing the issue upstream on GitHub to protect your privacy.

Can I prevent duplicate bug reports when filing defects on GitHub?

Yes, this defect tracking process prevents duplicate bug reports by deduping against existing GitHub issues before filing, ensuring only unique defects are submitted upstream.

Do I need GitHub access to automate steer plugin defect tracking?

Yes, you need GitHub access and specific commands for authentication and issue creation, requiring the `gh` CLI and `git` dependencies to successfully file the upstream bug report.

What is the best way to track defects in the steer plugin without manual issue creation?

The best way to track defects without manual issue creation is using automated reporting to dedupe, scrub secrets, and file bug reports directly to the GitHub repository upstream.

Why does automated defect reporting require git and gh dependencies?

Automated defect reporting requires `git` and `gh` dependencies because the process authenticates and creates issues directly on GitHub upstream, needing these tools to interact with the repository.