outside-to-issue

Convert review files from outside/ into formatted issue files for a pull request.

567|82|Updated Mar 15, 2026

Search Tags:#automation #workflow #code review #documentation #pull request #issue tracking

Ready to run

npx skills add https://github.com/pedronauck/skills --skill outside-to-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: outside-to-issue
Source: https://github.com/pedronauck/skills/tree/main/skills/outside-to-issue
Command: npx skills add https://github.com/pedronauck/skills --skill outside-to-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the conversion of unstructured review notes taken outside of a direct code diff into a standardized issue format, streamlining the process of tracking feedback and action items for pull requests.

Core Features & Use Cases

Automated Issue Creation: Transforms review files from an 'outside' directory into properly formatted issue files.
Metadata Preservation: Retains original file paths, dates, and statuses from the review files.
Automatic Numbering: Intelligently determines the next available issue number to ensure sequential tracking.
Use Case: After a code review, you have notes on files not directly changed in the PR. This Skill converts those notes into trackable issues within your PR workflow.

Quick Start

Run the transformation script for pull request number 90.

Frequently Asked Questions about outside-to-issue

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

FAQPage Schema

How do I convert code review notes into trackable issues for a pull request?▼

The skill converts review files from the 'outside/' directory into formatted issue files within the 'issues/' directory, automatically determining the starting issue number and preserving metadata like file path, date, and status from the original review files.

How does automated issue numbering work when generating issues from review files?▼

Automated issue numbering works by intelligently determining the next available issue number to ensure sequential tracking, preserving metadata such as file path, date, and status from the original review files.

What is the best way to track feedback on files not included in a pull request diff?▼

The best way to track feedback on files not included in a pull request diff is to use a skill that transforms review files located in the 'outside/' directory into formatted issue files within the 'issues/' directory, preserving metadata like file path, date, and status.

Does the issue conversion process preserve the original file path and review status?▼

Yes, the issue conversion process preserves metadata such as file path, date, and status from the original review files, ensuring that all critical information is retained in the formatted issue files.

Can I use this workflow to automate documentation and issue tracking for code reviews?▼

Yes, you can use this workflow to automate documentation and issue tracking for code reviews by transforming review files located in the 'outside/' directory into formatted issue files within the 'issues/' directory for a given pull request.

Why should I use an automated script instead of manually creating issues from review notes?▼

You should use an automated script instead of manually creating issues from review notes because it automates the conversion of unstructured review notes into a standardized issue format, streamlining the process of tracking feedback and action items for pull requests.