[maxigimenez]

Summary

• add the repo-scoped $github-issue-workflow skill for either a specified issue or the best actionable open issue
• define an evidence-based relevance gate: implement valid work, request concrete missing details, or comment and close only clear duplicates, resolved reports, out-of-scope requests, or invalid reports
• carry actionable issues through repository checks, Conventional Commit, push, and a review-ready PR without auto-merging
• bump @16-bits-design/ui from 0.2.0 to 0.3.0 and finalize the Dialog and Alert release notes

Release rationale

The npm registry currently reports 0.2.0. The existing v0.2.1 repository tag still contains package version 0.2.0, so 0.3.0 is the next publishable version and correctly represents the backward-compatible public Dialog and Alert additions merged since 0.2.0.

Verification

• quick_validate.py .agents/skills/github-issue-workflow — passed (Skill is valid!)
• npm run check under Node 24.13.1 — passed
  • ESLint and TypeScript passed
  • Vitest: 31/31 tests passed
  • package verification: 22 public exports verified at @16-bits-design/ui@0.3.0
  • Storybook production build completed successfully
• npm pack --dry-run --json --cache /tmp/16-bits-design-npm-cache — passed; artifact identified as @16-bits-design/ui@0.3.0, 127 files, no repository skill files included
• git diff --cached --check — passed

Review notes

• The skill is intentionally repo-scoped at .agents/skills/github-issue-workflow.
• Ambiguous but potentially relevant issues remain open with focused questions; uncertainty alone is never a closure reason.
• Triage-only outcomes do not create empty PRs, and implementation PRs are never auto-merged.
• No visual changes are included in this PR.