Merge pull request #2 from NASA-PDS/create-pds-issue-skill

Add creating-pds-issues skill

Author: jordanpadams

CHANGELOG.md

@@ -1,14 +1,65 @@
 # Changelog
 
-All notable changes to this project will be documented in this file. 
+All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [X.Y.Z] - 2022-MM-DD
+## [Unreleased]
 
-### Added 
+### Added
 
-- 
--
--
+- **creating-pds-issues** skill - Creates GitHub issues in NASA-PDS repositories using official templates
+  - 6 template types: Bug, I&T Bug, Feature Request, Task, Vulnerability, Release Theme
+  - Auto-detection of current repository from git remote (origin → upstream fallback)
+  - Security-first with comprehensive PII/credential sanitization guidance
+  - Template caching (7-day refresh) to minimize GitHub API calls
+  - Configurable assignee via `PDS_ISSUE_ASSIGNEE` environment variable
+
+### Removed
+
+- **pds-status-reporter** skill - Moved to separate repository for focused development
+  - Product mapping configuration (`pds-products.yaml`) removed from shared resources
+
+### Changed
+
+- Updated skills count badge from 3 to 2
+- Reorganized repository structure without pds-status-reporter references
+- Updated all documentation (README.md, SKILLS_CATALOG.md, CLAUDE.md) to reflect current skill set
+
+## [1.0.0] - 2024-11-06
+
+### Added
+
+- **SKILLS_CATALOG.md** - Comprehensive browsable catalog of all available skills with:
+  - Detailed descriptions and use cases for each skill
+  - Organization by category, use case, and work stream
+  - Status indicators for skill maturity
+  - Quick install instructions
+  - Shared resources documentation
+- **MARKETPLACE_SETUP.md** - Complete guide for configuring repository as a discoverable skills marketplace
+  - GitHub topics and discoverability configuration
+  - Repository settings recommendations
+  - Issue template examples
+  - Promotion and maintenance strategies
+- **Marketplace badges** in README.md:
+  - Skills count badge
+  - License badge
+  - Claude Code compatibility badge
+- **Skills catalog link** prominently featured in README.md
+- **Skills overview table** in README.md for quick reference
+- **generating-release-notes** skill - Generates structured GitHub release notes with breaking change detection, categorization, and upload
+- **Shared resources** for cross-skill use:
+  - `shared-resources/pds-labels.yaml` - Canonical PDS label definitions
+
+### Changed
+
+- Transformed repository into browsable skills marketplace
+- Updated README.md with catalog-first approach and marketplace badging
+- Reorganized available skills section for better discoverability
+
+### Infrastructure
+
+- Repository structure designed for Claude Code automatic skill discovery
+- Support for both project-level (`.claude/skills/`) and personal (`~/.claude/skills/`) installations
+- Git submodule support for easier updates

CLAUDE.md

@@ -4,90 +4,114 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Repository Overview
 
-This repository contains Claude Code skills for NASA's Planetary Data System (PDS). Skills are reusable AI agents that perform specialized tasks within the Claude Code CLI environment.
-
-## Repository Structure
-
-- `release-notes/` - Release notes generation skill
-  - `SKILL.md` - Skill definition and prompt for generating GitHub release notes
-  - `templates/` - Template files for release note formatting
-  - `additional_resources/` - Supporting documentation including PDS label mapping
+This repository contains Claude Code skills for NASA's Planetary Data System (PDS). Skills are reusable AI agents that perform specialized tasks within the Claude Code CLI environment. There are no build commands, tests, or compilation steps - this is a documentation and configuration repository.
 
 ## Skills Architecture
 
 ### What is a Skill?
 
-Skills in this repository are defined by `SKILL.md` files that contain:
-1. **Frontmatter** (YAML format) with `name` and `description` fields
-2. **Detailed instructions** for Claude Code on how to execute the skill
-3. **Input/output specifications** defining expected parameters and results
-4. **Style rules and algorithms** that govern skill behavior
+Skills are defined by `SKILL.md` files with YAML frontmatter and detailed instructions. Structure:
+
+```
+skill-name/
+├── SKILL.md              # Main skill definition with frontmatter and instructions
+├── scripts/              # Optional: Node.js scripts for complex operations
+├── resources/            # Optional: Configuration files (YAML/JSON)
+└── additional files/     # Optional: Templates, documentation, references
+```
 
-### Release Notes Skill
+**SKILL.md anatomy:**
+```yaml
+---
+name: skill-name
+description: Brief description triggering the skill
+---
+# Full instructions for Claude Code to execute the skill
+```
 
-Location: `release-notes/SKILL.md`
+### Available Skills
 
-This skill generates structured, user-friendly GitHub release notes with:
-- Automatic categorization of changes (Breaking Changes, New, Improvements, Fixes, Security, etc.)
-- **Breaking changes detection and prominence** - any breaking changes MUST appear first with ⚠️ warning
-- Executive summaries in "Highlights" section
-- Mandatory GitHub links for all changes
-- Optional upload to GitHub releases via `gh` CLI
+**1. generating-release-notes/** - Generates structured GitHub release notes
+- Categorizes PRs/issues by labels (Breaking → Highlights → New → Improvements → Fixes → Security → etc.)
+- **Critical rule:** Breaking changes ALWAYS appear first with ⚠️ warning
+- Requires GitHub CLI (`gh`) for optional upload to releases
+- Label mapping: `generating-release-notes/label-mapping.md`
 
-**Key Inputs:**
-- `repo` - GitHub org/repo (e.g., `NASA-PDS/doi-service`)
-- `tag/version` - Release version (e.g., `v1.6.0`)
-- `date` - Release date
-- `changes` - Structured list of PRs/issues with labels, numbers, URLs
-- `compare_url` - GitHub compare link
-- `upload` (optional) - Boolean to upload via `gh` CLI
+**2. creating-pds-issues/** - Creates GitHub issues using NASA-PDS templates
+- Supports 6 template types: Bug, I&T Bug, Feature, Task, Vulnerability, Release Theme
+- Auto-detects repository from git remote (origin → upstream fallback)
+- Security-first with PII/credential sanitization
+- Template caching (7-day refresh) to minimize API calls
+- Requires GitHub CLI (`gh`) and Node.js v18+ for caching scripts
 
-**Label Mapping:**
-The skill uses PDS-specific GitHub labels to categorize changes. See `release-notes/additional_resources/label_mapping.md` for the complete mapping of PDS labels to release note sections.
+## Shared Resources
 
-**Critical Rules:**
-1. Breaking changes ALWAYS appear first if present
-2. Every bullet point MUST include a GitHub link
-3. Highlights should be outcome-focused (3-6 bullets)
-4. Section order is strict: Breaking → Highlights → New → Improvements → Fixes → Security → Deprecations → Compatibility → Upgrade notes → Known issues → Links
+**shared-resources/pds-labels.yaml** - Canonical PDS GitHub label definitions
+- Used by multiple skills for consistent label interpretation
+- Defines semantics for priority, severity, type, status labels
 
-## Development Workflow
+## Key Workflows
 
 ### Adding a New Skill
 
-1. Create a new directory under the repository root: `<skill-name>/`
-2. Add a `SKILL.md` file with:
-   - YAML frontmatter containing `name` and `description`
-   - Comprehensive instructions for Claude Code
+1. Create directory: `<skill-name>/`
+2. Create `SKILL.md` with:
+   - YAML frontmatter (`name`, `description`)
+   - Comprehensive instructions for autonomous execution
    - Input/output specifications
    - Style rules and edge cases
-3. Add supporting resources in subdirectories as needed (templates, additional_resources)
-
-### Testing Skills
-
-Skills are invoked within Claude Code sessions. Test by:
-1. Providing sample inputs that match the skill's expected format
-2. Verifying outputs follow the specified structure and style rules
-3. Testing edge cases documented in the skill definition
-
-### Documentation
-
-- Update `CHANGELOG.md` following [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) format
-- Use [Semantic Versioning](https://semver.org/spec/v2.0.0.html) for version numbers
-- The README.md is a template file - populate it with actual project information
+3. Add supporting resources as needed (scripts/, resources/, templates/)
+4. Update README.md "Available Skills" section
+5. Update CHANGELOG.md following [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 
 ## PDS Context
 
-This repository is part of NASA's Planetary Data System (PDS) Engineering Node (EN). Skills are designed to support PDS development workflows, particularly around release management and GitHub operations.
+### Label System Philosophy
 
-### PDS Label System
+PDS uses GitHub labels for categorization and prioritization:
 
-PDS uses a comprehensive GitHub label system for issue/PR categorization:
-- `backwards-incompatible` / `breaking-change` - Breaking changes requiring major version bump
-- `security` - Security vulnerabilities or concerns
+**Type labels:**
+- `backwards-incompatible` / `breaking-change` - Breaking changes (major version bump)
+- `security` - Security vulnerabilities
 - `requirement` - New feature user stories
 - `enhancement` - Improvements to existing features
 - `bug` - Bug fixes
-- `maintenance` - Internal maintenance (usually omitted from release notes)
+- `theme` - Release Themes (planned stakeholder priorities)
+
+**Priority labels (optional):**
+- `p.must-have` / `p.should-have` / `p.could-have`
+
+**Status labels (exclusion):**
+- `duplicate` / `invalid` / `wontfix` / `icebox` - Excluded from reports
+
+**Planning labels (NOT excluded):**
+- `sprint-backlog` / `release-backlog` / `B##.#` (build tracking) / `i&t.*` (testing)
+
+Complete definitions: `shared-resources/pds-labels.yaml`
+
+### GitHub CLI Requirements
+
+Skills use GitHub CLI (`gh`) for GitHub operations:
+```bash
+# Verify authentication
+gh auth status
+
+# Re-authenticate if needed
+gh auth login
+
+# Check rate limits (5000/hour when authenticated)
+gh api rate_limit
+```
+
+### Work Streams
+
+PDS organizes work into three streams:
+1. **Core Data Services** - Registry, validation, data dictionaries
+2. **Web Modernization** - Websites, design system, CMS
+3. **Planetary Data Cloud** - Cloud migration, infrastructure
+
+## Documentation Standards
 
-Many other labels exist for planning, triage, and project tracking but are not included in user-facing release notes. See `release-notes/additional_resources/label_mapping.md` for the complete reference.
+- **CHANGELOG.md**: [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) format
+- **Versioning**: [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
+- **Skill descriptions**: Must be clear enough for Claude Code to auto-invoke based on user requests

README.md

@@ -9,9 +9,14 @@
 <pre align="center">Reusable AI agents for NASA Planetary Data System workflows in Claude Code</pre>
 
 [![SLIM](https://img.shields.io/badge/Best%20Practices%20from-SLIM-blue)](https://nasa-ammos.github.io/slim/)
+![Skills](https://img.shields.io/badge/skills-2-brightgreen)
+![License](https://img.shields.io/badge/license-Apache%202.0-blue)
+[![Claude Code](https://img.shields.io/badge/Claude%20Code-Compatible-purple)](https://claude.ai/code)
 
 This repository contains [Claude Code skills](https://docs.claude.com/en/docs/claude-code/skills) for NASA's Planetary Data System (PDS) Engineering Node. Skills are specialized AI agents that automate complex tasks within the [Claude Code CLI environment](https://claude.ai/code).
 
+**🎯 [Browse Skills Catalog →](SKILLS_CATALOG.md)** - View all available skills with detailed descriptions and use cases
+
 ## Table of Contents
 
 - [What are Claude Code Skills?](#what-are-claude-code-skills)
@@ -40,25 +45,16 @@ Skills help automate repetitive or complex workflows, making development more ef
 
 ## Available Skills
 
-### 📝 Release Notes Generator
-
-**Location:** `release-notes/`
-
-Generates structured, user-friendly GitHub release notes from PR/issue data with:
+**📖 [View Full Skills Catalog →](SKILLS_CATALOG.md)** - Browse all skills with detailed descriptions, use cases, and examples
 
-- Automatic categorization (Breaking Changes, New Features, Improvements, Fixes, Security)
-- Prominent breaking changes warnings (⚠️)
-- Executive summaries in "Highlights" section
-- Mandatory GitHub links for all changes
-- PDS-specific label mapping
-- Optional upload to GitHub releases via `gh` CLI
+### Quick Overview
 
-**Use cases:**
-- Creating release notes for PDS software releases
-- Generating changelog summaries from GitHub data
-- Ensuring consistent release note formatting across PDS projects
+| Skill | Description | Use Cases |
+|-------|-------------|-----------|
+| **[generating-release-notes](generating-release-notes/SKILL.md)** | Generate structured GitHub release notes with breaking changes, categorization, and upload | Software releases, changelogs, version announcements |
+| **[creating-pds-issues](creating-pds-issues/SKILL.md)** | Create GitHub issues using official NASA-PDS templates with security sanitization | Bug reports, feature requests, I&T bugs, security vulnerabilities |
 
-See [release-notes/SKILL.md](release-notes/SKILL.md) for detailed documentation.
+**Total Skills:** 2 production-ready skills for PDS workflows
 
 ## Installation
 
@@ -154,39 +150,43 @@ claude "Generate release notes for NASA-PDS/doi-service version v1.6.0"
 
 Claude analyzes your request, identifies that the release-notes skill is relevant, and executes it autonomously.
 
-**Available skills:**
-- `release-notes` - Generates structured GitHub release notes
-
-See individual skill documentation for detailed input specifications and examples.
+See the [Skills Catalog](SKILLS_CATALOG.md) or individual skill documentation for detailed input specifications and examples.
 
 ## Adding a New Skill
 
-1. Create a new directory: `<skill-name>/`
-2. Add a `SKILL.md` file with:
-   ```yaml
-   ---
-   name: skill-name
-   description: Brief description of what the skill does
-   ---
-   ```
-3. Add comprehensive instructions, input/output specs, and style rules
-4. Include supporting resources in subdirectories (templates, additional_resources, etc.)
-5. Update this README with your new skill in the "Available Skills" section
-6. Test thoroughly with sample inputs
-
-See [CLAUDE.md](CLAUDE.md) for detailed development guidance.
+See the [Skills Catalog](SKILLS_CATALOG.md) for examples and [CLAUDE.md](CLAUDE.md) for detailed development guidance.
+
+**Quick steps:**
+1. Create a new directory: `<skill-name>/` (use gerund form: `generating-*`, `processing-*`)
+2. Add a `SKILL.md` file with YAML frontmatter and instructions
+3. Test with sample inputs
+4. Update [SKILLS_CATALOG.md](SKILLS_CATALOG.md) with your new skill
+5. Submit a pull request
+
+For marketplace configuration and GitHub setup, see [docs/MARKETPLACE_SETUP.md](docs/MARKETPLACE_SETUP.md).
 
 ## Repository Structure
 
 ```
 pds-claude-skills/
-├── release-notes/          # Release notes generation skill
-│   ├── SKILL.md           # Skill definition and instructions
-│   ├── templates/         # Release note templates
-│   └── additional_resources/  # PDS label mapping and docs
-├── CLAUDE.md              # Developer guidance for Claude Code
-├── README.md              # This file
-└── CHANGELOG.md           # Project changelog
+├── generating-release-notes/   # Release notes generation skill
+│   ├── SKILL.md                # Skill definition and instructions
+│   ├── templates/              # Release note templates
+│   └── resources/              # Supporting resources
+├── creating-pds-issues/        # GitHub issue creation skill
+│   ├── SKILL.md                # Skill definition and instructions
+│   ├── scripts/                # Helper scripts for template caching
+│   └── resources/              # Issue templates and config
+├── shared-resources/           # Shared across all skills
+│   └── pds-labels.yaml         # Canonical PDS label definitions
+├── docs/                       # Marketplace documentation
+│   ├── MARKETPLACE_SETUP.md    # GitHub configuration guide
+│   ├── MARKETPLACE_COMPLETE.md # Transformation summary
+│   └── PRODUCTS_README.md      # Product mapping documentation
+├── SKILLS_CATALOG.md           # Browse all available skills
+├── CLAUDE.md                   # Developer guidance for Claude Code
+├── README.md                   # This file
+└── CHANGELOG.md                # Project changelog
 ```
 
 ## Contributing