outside-to-issue

Included with Lifetime

$97 forever

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.

Code Review

What this skill does

# Outside to Issue

Transform outside-of-diff review files into properly formatted issue files for PR review tracking.

## Overview

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.

## Usage

Run the transformation script for a specific PR:

```bash
scripts/transform-outside-to-issues.sh --pr <PR_NUMBER>
```

**Example:**
```bash
scripts/transform-outside-to-issues.sh --pr 90
```

## What It Does

1. **Finds all outside files**: Reads all `.md` files from `ai-docs/reviews-pr-<PR>/outside/` directory
2. **Determines starting issue number**: Automatically finds the highest existing issue number and starts numbering from the next available number
3. **Transforms each file**: Converts outside review files into issue format with:
   - Issue number and title
   - File path from the review
   - Date and status
   - Body section containing the review details
   - Footer indicating it's from outside-of-diff review

## File Structure

The 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
    └── ...
```

## Output Format

Each transformed issue file follows this format:

```markdown
# Issue <NUMBER> - Outside-of-diff

**File:** `<file-path>`
**Date:** <date>
**Status:** <status>

## Body

<review-details-content>

---

_Generated from outside-of-diff review_
```

## Example

For PR 90 with 18 outside files:

```bash
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
```

## Notes

- The script automatically determines the starting issue number based on existing issues
- Files are processed in sorted order (alphabetically by filename)
- All metadata (file path, date, status) is preserved from the original outside file
- The Details section content becomes the Body section in the issue file
- The script creates the `issues/` directory if it doesn't exist

## Related Commands

- `read_pr_issues.sh` - Read and display PR review issues
- `resolve_pr_issues.py` - Mark issues as resolved and update GitHub threads
- `pr-fix` command - Fix issues for a given PR

Files: 1

Size: 3.1 KB

Complexity: 15/100

Category: Code Review

Source: https://github.com/pedronauck/skills/tree/main/skills/mine/outside-to-issue

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts