skills/mine/outside-to-issue/SKILL.md
Transform outside-of-diff review files into properly formatted issue files for a given PR. Use when converting review files from ai-docs/reviews-pr-<PR>/outside/ into issue format in ai-docs/reviews-pr-<PR>/issues/. Automatically determines starting issue number and preserves all metadata (file path, date, status) from original review files. Don't use for inline-diff review files, non-PR review artifacts, or creating GitHub issues directly.
npx skillsauth add pedronauck/skills outside-to-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform outside-of-diff review files into properly formatted issue files for PR review tracking.
This skill converts review files from the outside/ directory into standardized issue files in the issues/ directory, following the project's issue template format. The transformation preserves all metadata and automatically handles issue numbering.
Run the transformation script for a specific PR:
scripts/transform-outside-to-issues.sh --pr <PR_NUMBER>
Example:
scripts/transform-outside-to-issues.sh --pr 90
.md files from ai-docs/reviews-pr-<PR>/outside/ directoryThe script expects this directory structure:
ai-docs/reviews-pr-<PR>/
├── outside/
│ ├── 002-outside_01_<file-path>.md
│ ├── 002-outside_02_<file-path>.md
│ └── ...
└── issues/
├── 001-issue.md
├── 002-issue.md
└── ...
Each transformed issue file follows this format:
# Issue <NUMBER> - Outside-of-diff
**File:** `<file-path>`
**Date:** <date>
**Status:** <status>
## Body
<review-details-content>
---
_Generated from outside-of-diff review_
For PR 90 with 18 outside files:
scripts/transform-outside-to-issues.sh --pr 90
Output:
Created: issues/026-issue.md
Created: issues/027-issue.md
...
Created: issues/043-issue.md
Transformation complete! Created issues starting from 26
issues/ directory if it doesn't existread_pr_issues.sh - Read and display PR review issuesresolve_pr_issues.py - Mark issues as resolved and update GitHub threadspr-fix command - Fix issues for a given PRtools
Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.
development
Executes real-user QA sessions through public interfaces using personas, journeys, exploratory charters, test tours, edge-case probes, CFR checks, and browser evidence. Reads qa-report artifacts from <qa-output-path>/qa/ when present, captures issues/screenshots/reports under the same output tree, and classifies bugs by user impact. Use when validating a release candidate, migration, refactor, or user-facing change against production-like behavior. Do not use for AI implementation audits, task-status reconciliation, CI gate runs, integration/security/performance templates, or flaky-test triage; use agent-output-audit for those.
development
Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.
data-ai
Creates and maintains Knowledge Base topics from YouTube channels by resolving recent or full uploads, scaffolding yt-channels topics, ingesting transcripts through kb ingest youtube, and validating/indexing the result. Use when turning a YouTube channel into a Karpathy KB topic. Do not use for single-video ingestion, general video summaries, or non-YouTube sources.