pedronauck/outside-to-issue
skills/deprecated/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.
$ install --global
skillsauthnpx skillsauth add pedronauck/skills outside-to-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 6:20 AM105.6s1 file scanned
SKILL.md
- name:
- outside-to-issue
- description:
- 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.
- author:
- Pedro Nauck
- github:
- https://github.com/pedronauck
- repository:
- https://github.com/pedronauck/skills
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:
scripts/transform-outside-to-issues.sh --pr <PR_NUMBER>
Example:
scripts/transform-outside-to-issues.sh --pr 90
What It Does
- Finds all outside files: Reads all
.mdfiles fromai-docs/reviews-pr-<PR>/outside/directory - Determines starting issue number: Automatically finds the highest existing issue number and starts numbering from the next available number
- 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:
# 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:
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 issuesresolve_pr_issues.py- Mark issues as resolved and update GitHub threadspr-fixcommand - Fix issues for a given PR
Related Skills
pedronauck/deep-review
development
VerifiedTrustedCommunity
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
520SKILL.mdUpdated Jul 18, 2026
pedronauck/herdr-orchestration
tools
VerifiedTrustedCommunity
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
520SKILL.mdUpdated Jul 11, 2026
pedronauck/tanstack
tools
VerifiedTrustedCommunity
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
520SKILL.mdUpdated Jun 13, 2026
pedronauck/impeccable
development
VerifiedTrustedCommunity
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
520SKILL.mdUpdated May 14, 2026