aiwg-issue

Solid

AIWG project issue filing only — templates, environment capture, duplicate detection, and import flow for AIWG tracker reports; not for general issue audits or address-issues processing

AI & Automation 142 stars 21 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Filing AIWG Issues You are helping a user (or yourself, as an autonomous agent) file a high-quality issue. The bar is set by the recent tester-report import sweep (Gitea #1264–#1269): environment captured, exact commands, error text in code blocks, suggested fix paths. This is an **AIWG-specific kernel capability**. Use it for filing, importing, or triaging the quality of issue reports about AIWG itself. Do **not** use this skill for general backlog processing: - Use `issue-audit` / `audit-issues` when the user asks to audit open issues, triage a backlog, find duplicates, review stale issues, or rank work. - Use `address-issues` when the user asks to fix, process, or work through issues. - Treat `aiwg-*` skill names as AIWG product/workspace capabilities, not as the generic issue-processing surface. ## When this fires Natural-language triggers: - "file an AIWG issue" - "report an AIWG bug" - "import this AIWG issue from GitHub" - "I want to file an issue" - "How do I report a bug?" - "Help me write up a bug report" - "What template should I use?" - "Should I file a new issue or comment on an existing one?" - "Import this report from GitHub" / "from Discord" / "from email" Non-triggers: - "audit open issues" - "triage the issue backlog" - "review stale issues" - "address issues" - "process open issues" ## Template selection | Template | When to use | Path | |---|---|---| | `bug-report.md` | One concrete defect with a reproduction | `.gitea/ISSUE_TEMPLATE/bug-repor...

Details

Author
jmagly
Repository
jmagly/aiwg
Created
9 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ai-engineering-issue

Files an upstream bug or improvement report against `arcasilesgroup/ai-engineering` (the framework repo) with strict seven-vector redaction, mandatory human confirmation, and an archived sanitized copy. Trigger for 'report this upstream', 'file an ai-engineering bug', 'this looks like a framework bug', 'tell anthropic / arcasiles about this'. Not for your own project's board (use /ai-issue); not for security disclosure (use the private channel listed in CONSTITUTION.md).

49 Updated today
arcasilesgroup
AI & Automation Listed

ai-issue

Creates a project work-item (issue / task / story) on the user's configured board: routes by manifest `work_items.provider` (GitHub Projects v2 or Azure DevOps), composes title + body + labels, attaches to the active board, and confirms a clickable link. Trigger for 'open an issue', 'file a bug', 'create a task', 'add this to the backlog', 'log a work item'. Not for upstream framework bugs (use /ai-engineering-issue); not for board configuration (use /ai-board discover); not for committing code (use /ai-commit).

49 Updated today
arcasilesgroup
AI & Automation Solid

issue-tracker

Track and manage project issues with escalation and resolution workflows

1,160 Updated today
a5c-ai
Code & Development Listed

issue-writing

Use when drafting, revising, triaging, or reviewing GitHub issue titles and bodies, bug reports, feature requests, internal implementation issues, acceptance criteria, scope boundaries, decomposition notes, and links to supporting documents. Handles issue framing, scope, title shape, checkable outcomes, and when context belongs somewhere else. Pair with content-styleguide for deeper prose quality.

0 Updated 6 days ago
birdseyeglobal
AI & Automation Listed

mkjira-issue

JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).

14 Updated today
ngocsangyem