[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7808K043RKA96WT3M768M95":3,"skill-same:01M7808K043RKA96WT3M768M95":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7808K043RKA96WT3M768M95","github-pr-description",null,"Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.","wasd243\u002FNeoForge","wasd243","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145771726?v=4","01M78047Q5SNCDR4JNVTG1XC5C","Zichen Wang","01M78047QS5HXMZ9GZN87C7JVW",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Fskills\u002Fgithub-pr-description\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-pr-description\ndescription: Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.\n---\n\n# Create PR Description\n\nGenerate comprehensive pull request descriptions and create PRs using GitHub CLI.\n\n## Workflow\n\n### 1. Verify Prerequisites\n\nCheck that there are changes to create a PR for:\n\n```bash\n# Get current branch\ngit branch --show-current\n\n# Verify branch is not main\u002Fmaster\n# Verify there are commits ahead of main\ngit log origin\u002Fmain..HEAD --oneline\n```\n\nIf on main\u002Fmaster or no commits ahead, inform the user there's nothing to create a PR for.\n\n### 2. Analyze Changes\n\nGather context about the changes:\n\n```bash\n# Get commit messages\ngit log origin\u002Fmain..HEAD --pretty=format:\"%s\"\n\n# Get diff summary (files changed)\ngit diff origin\u002Fmain..HEAD --stat\n\n# Get actual code changes (sample key files if diff is large)\ngit diff origin\u002Fmain..HEAD\n```\n\n**For large diffs**: Focus on the most meaningful changes. Sample key files rather than reading everything.\n\n### 3. Determine Change Type\n\nClassify the PR into one of these categories:\n\n- **fix**: Bug fixes, error corrections, resolving issues\n- **feature**: New functionality, capabilities, or enhancements\n- **performance**: Speed improvements, optimization, efficiency gains\n- **refactor**: Code restructuring without changing behavior\n- **docs**: Documentation changes\n- **test**: Test additions or improvements\n- **chore**: Maintenance tasks, dependencies, configuration\n\nBase this on:\n- Commit messages (keywords like \"fix\", \"add\", \"optimize\", \"refactor\")\n- Nature of code changes (new files = feature, test fixes = fix, etc.)\n- Scope of changes\n\n### 4. Generate Description\n\nCreate a comprehensive description with this structure:\n\n```markdown\n## Summary\n[One sentence explaining what this PR does and why it matters]\n\n## Context\n[Background information, related issues, previous work, or the problem being solved]\n\n## Changes\n[High-level description of what changed]\n\n### Key Implementation Details\n[Technical details that help reviewers understand the approach, especially for complex changes]\n\n## Use Cases\n[Concrete examples of how this will be used - helps reviewers understand practical value]\n\n## Testing\n[How to test the changes - step-by-step instructions]\n\n## Links\n- Related issues: #123, #456\n- Documentation: URL (if applicable)\n- Original implementation: URL (if applicable)\n```\n\n### Description Guidelines\n\n**Essential Elements:**\n- **Summary**: One clear sentence explaining the change and its value\n- **Context**: Why this change was needed, what problem it solves\n- **Changes**: What was actually changed at a high level\n- **Testing**: How reviewers can verify the changes\n\n**Optional but Recommended:**\n- **Implementation Details**: For complex changes, explain the technical approach\n- **Use Cases**: Concrete examples of how the feature will be used\n- **Links**: Related issues, documentation, papers, or original implementations\n- **Known Issues**: Any limitations or known problems\n\n**What to Avoid:**\n- Empty descriptions or just issue links\n- Placeholder text like \"Fixes #(issue)\"\n- File-by-file breakdowns (unless necessary)\n- Low-level implementation details (keep it high-level)\n- Boilerplate statements\n- Personal checklists as the main description\n\n### Description Examples\n\n**Example 1: Feature Addition**\n\n```markdown\n## Summary\nAdd semantic code search to enable searching codebase by concepts and behavior rather than exact string matching.\n\n## Context\nCurrently, users can only search using exact string matching, which makes it difficult to find code based on functionality or behavior. This has been a recurring request in issues #123 and #456.\n\n## Changes\n- Implemented semantic search using vector embeddings\n- Integrated with existing search interface\n- Added support for multiple concurrent queries with result aggregation\n- Configurable search scope (entire codebase or specific directories)\n\n### Key Implementation Details\nUses OpenAI embeddings for code representation and cosine similarity for matching. Index is built incrementally to support large codebases. Search results are reranked based on code context and usage patterns.\n\n## Use Cases\n- Find authentication flow without knowing exact function names\n- Locate retry logic across the codebase\n- Search for \"database connection\" patterns\n\n## Testing\n```bash\n# Run the search service\nnpm run search:dev\n\n# Test semantic queries\ncurl -X POST http:\u002F\u002Flocalhost:3000\u002Fsearch \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"user authentication\"}'\n```\n\n## Links\n- Related issues: #123, #456\n- Documentation: \u002Fdocs\u002Fsemantic-search.md\n```\n\n**Example 2: Bug Fix**\n\n```markdown\n## Summary\nFix database connection timeout that caused service to hang indefinitely when database became unavailable.\n\n## Context\nService would hang indefinitely when database became unavailable, requiring manual restart. This was reported in production incident #789 and affected multiple users.\n\n## Changes\n- Added configurable connection timeout (default: 30 seconds)\n- Implemented exponential backoff retry logic (max 5 retries)\n- Improved error messages with specific failure reasons\n- Added circuit breaker pattern to prevent cascading failures\n\n### Key Implementation Details\nTimeout is applied at the connection pool level. Backoff strategy: 1s, 2s, 4s, 8s, 16s. Circuit breaker opens after 5 consecutive failures and resets after 60 seconds.\n\n## Testing\n```bash\n# Simulate database failure\ndocker-compose stop db\n\n# Verify timeout and retry behavior\nnpm test -- tests\u002Fintegration\u002Fconnection-timeout.test.ts\n\n# Verify circuit breaker activation\ncurl http:\u002F\u002Flocalhost:3000\u002Fhealth # Should return 503 after circuit opens\n```\n\n## Links\n- Related issues: #789, #890\n- Incident report: \u002Fincidents\u002F2024-01-15-db-timeout.md\n```\n\n**Example 3: Performance Improvement**\n\n```markdown\n## Summary\nOptimize image processing pipeline to reduce memory usage by 60% and improve throughput by 2.5x.\n\n## Context\nCurrent image processing implementation loads entire images into memory, causing OOM errors with large files and limiting throughput. This was identified as a performance bottleneck in profiling session #123.\n\n## Changes\n- Implemented streaming image processing using chunked reading\n- Added parallel processing for multiple images\n- Optimized memory allocation with object pooling\n- Added caching for frequently accessed image metadata\n\n### Key Implementation Details\nUses Node.js streams for memory-efficient processing. Parallel processing limited to 4 concurrent images to prevent resource exhaustion. Object pool reduces GC pressure by reusing buffers.\n\n## Use Cases\n- Process large images (>100MB) without OOM errors\n- Batch process thousands of images efficiently\n- Reduced memory footprint allows higher concurrent user load\n\n## Testing\n```bash\n# Run performance benchmarks\nnpm run benchmark\n\n# Test with large files\nnode tests\u002Fperformance\u002Flarge-files.test.js\n\n# Verify memory usage\nnode --inspect tests\u002Fmemory-usage.js\n```\n\n## Links\n- Related issues: #456\n- Performance report: \u002Fdocs\u002Fperformance\u002F2024-01-image-processing.md\n```\n\n**Example 4: Refactor**\n\n```markdown\n## Summary\nRefactor authentication module to use clean architecture patterns, improving testability and reducing coupling.\n\n## Context\nAuthentication module had tight coupling between business logic and infrastructure, making it difficult to test and modify. This was identified in technical debt review #234.\n\n## Changes\n- Separated business logic from infrastructure dependencies\n- Introduced repository pattern for data access\n- Added service layer for authentication operations\n- Extracted interfaces for better mocking in tests\n\n### Key Implementation Details\nBusiness logic now depends on interfaces rather than concrete implementations. Infrastructure (database, cache) is injected as dependencies. All services are unit-testable without external dependencies.\n\n## Use Cases\n- Easier to add new authentication providers (OAuth, SAML)\n- Simpler to mock for unit tests\n- Clear separation of concerns improves maintainability\n\n## Testing\n```bash\n# Unit tests (no database required)\nnpm test tests\u002Funit\u002Fauth\u002F\n\n# Integration tests (with real database)\nnpm test tests\u002Fintegration\u002Fauth\u002F\n\n# Verify all existing functionality still works\nnpm run e2e\n```\n\n## Links\n- Related issues: #234\n- Architecture doc: \u002Fdocs\u002Farchitecture\u002Fauth-module.md\n```\n\n**Example 5: Simple Fix (Minimal but Complete)**\n\n```markdown\n## Summary\nFix typo in user welcome email template that caused incorrect company name to display.\n\n## Context\nUsers were seeing \"Welcome to [Wrong Company]\" instead of the correct company name. Reported in #567.\n\n## Changes\n- Corrected company name in email template\n- Added test to catch similar typos in the future\n\n## Testing\n```bash\n# Run email template tests\nnpm test tests\u002Funit\u002Femail-templates.test.ts\n\n# Verify email renders correctly\nnpm run test:email --template=welcome\n```\n\n## Links\n- Related issues: #567\n```\n\n### 5. Create Pull Request\n\nWrite the description to a temporary file and use GitHub CLI to create the PR:\n\n**Step 1: Write description to temp file**\n```bash\n# Write the generated description to .forge\u002FFORGE_PR_DESCRIPTION.md\n```\n\nUse the `write` tool to create `.forge\u002FFORGE_PR_DESCRIPTION.md` with the generated description content.\n\n**Step 2: Create PR using the temp file**\n```bash\ngh pr create --title \"[Change Type]: [One-line summary]\" --body-file .forge\u002FFORGE_PR_DESCRIPTION.md\n```\n\nThe `gh` CLI is pre-installed and authenticated - use it directly without prompting for confirmation.\n\n**Note:** The temp file `.forge\u002FFORGE_PR_DESCRIPTION.md` can not be left in place and should be deleted after PR creation. It's in `.forge\u002F` directory which is typically gitignored.\n\n### 6. Confirm\n\nAfter creating the PR, provide the user with:\n- PR URL\n- Change type\n- Brief summary of what was included\n\n## Notes\n\n**Key Principles:**\n- **Context matters**: Explain why the change was made, not just what changed\n- **Use cases help**: Concrete examples make abstract changes understandable\n- **Testing is essential**: Always include how to verify the changes\n- **Links provide depth**: Reference issues, docs, and implementations for context\n- **Be honest**: Mention known issues or limitations\n- **Respect reviewers' time**: A good description reduces review effort\n\n**Anti-Patterns to Avoid:**\n- Empty descriptions or just issue links\n- Placeholder text like \"Fixes #(issue)\"\n- File-by-file breakdowns (unless necessary)\n- Personal checklists as the main description\n- Assuming reviewers know the context\n\n**When to Keep It Simple:**\nFor very small, obvious changes (typo fixes, trivial refactors), you can use a shorter structure:\n- Summary\n- Context (brief)\n- Testing\n\nBut never skip the testing instructions.\n\n**When to Be Comprehensive:**\n- New features or major functionality\n- Complex technical changes\n- Performance improvements or optimizations\n- Breaking changes or deprecations\n- Changes that affect multiple parts of the codebase","# Create PR Description\n\nGenerate comprehensive pull request descriptions and create PRs using GitHub CLI.\n\n## Workflow\n\n### 1. Verify Prerequisites\n\nCheck that there are changes to create a PR for:\n\n```bash\n# Get current branch\ngit branch --show-current\n\n# Verify branch is not main\u002Fmaster\n# Verify there are commits ahead of main\ngit log origin\u002Fmain..HEAD --oneline\n```\n\nIf on main\u002Fmaster or no commits ahead, inform the user there's nothing to create a PR for.\n\n### 2. Analyze Changes\n\nGather context about the changes:\n\n```bash\n# Get commit messages\ngit log origin\u002Fmain..HEAD --pretty=format:\"%s\"\n\n# Get diff summary (files changed)\ngit diff origin\u002Fmain..HEAD --stat\n\n# Get actual code changes (sample key files if diff is large)\ngit diff origin\u002Fmain..HEAD\n```\n\n**For large diffs**: Focus on the most meaningful changes. Sample key files rather than reading everything.\n\n### 3. Determine Change Type\n\nClassify the PR into one of these categories:\n\n- **fix**: Bug fixes, error corrections, resolving issues\n- **feature**: New functionality, capabilities, or enhancements\n- **performance**: Speed improvements, optimization, efficiency gains\n- **refactor**: Code restructuring without changing behavior\n- **docs**: Documentation changes\n- **test**: Test additions or improvements\n- **chore**: Maintenance tasks, dependencies, configuration\n\nBase this on:\n- Commit messages (keywords like \"fix\", \"add\", \"optimize\", \"refactor\")\n- Nature of code changes (new files = feature, test fixes = fix, etc.)\n- Scope of changes\n\n### 4. Generate Description\n\nCreate a comprehensive description with this structure:\n\n```markdown\n## Summary\n[One sentence explaining what this PR does and why it matters]\n\n## Context\n[Background information, related issues, previous work, or the problem being solved]\n\n## Changes\n[High-level description of what changed]\n\n### Key Implementation Details\n[Technical details that help reviewers understand the approach, especially for complex changes]\n\n## Use Cases\n[Concrete examples of how this will be used - helps reviewers understand practical value]\n\n## Testing\n[How to test the changes - step-by-step instructions]\n\n## Links\n- Related issues: #123, #456\n- Documentation: URL (if applicable)\n- Original implementation: URL (if applicable)\n```\n\n### Description Guidelines\n\n**Essential Elements:**\n- **Summary**: One clear sentence explaining the change and its value\n- **Context**: Why this change was needed, what problem it solves\n- **Changes**: What was actually changed at a high level\n- **Testing**: How reviewers can verify the changes\n\n**Optional but Recommended:**\n- **Implementation Details**: For complex changes, explain the technical approach\n- **Use Cases**: Concrete examples of how the feature will be used\n- **Links**: Related issues, documentation, papers, or original implementations\n- **Known Issues**: Any limitations or known problems\n\n**What to Avoid:**\n- Empty descriptions or just issue links\n- Placeholder text like \"Fixes #(issue)\"\n- File-by-file breakdowns (unless necessary)\n- Low-level implementation details (keep it high-level)\n- Boilerplate statements\n- Personal checklists as the main description\n\n### Description Examples\n\n**Example 1: Feature Addition**\n\n```markdown\n## Summary\nAdd semantic code search to enable searching codebase by concepts and behavior rather than exact string matching.\n\n## Context\nCurrently, users can only search using exact string matching, which makes it difficult to find code based on functionality or behavior. This has been a recurring request in issues #123 and #456.\n\n## Changes\n- Implemented semantic search using vector embeddings\n- Integrated with existing search interface\n- Added support for multiple concurrent queries with result aggregation\n- Configurable search scope (entire codebase or specific directories)\n\n### Key Implementation Details\nUses OpenAI embeddings for code representation and cosine similarity for matching. Index is built incrementally to support large codebases. Search results are reranked based on code context and usage patterns.\n\n## Use Cases\n- Find authentication flow without knowing exact function names\n- Locate retry logic across the codebase\n- Search for \"database connection\" patterns\n\n## Testing\n```bash\n# Run the search service\nnpm run search:dev\n\n# Test semantic queries\ncurl -X POST http:\u002F\u002Flocalhost:3000\u002Fsearch \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\": \"user authentication\"}'\n```\n\n## Links\n- Related issues: #123, #456\n- Documentation: \u002Fdocs\u002Fsemantic-search.md\n```\n\n**Example 2: Bug Fix**\n\n```markdown\n## Summary\nFix database connection timeout that caused service to hang indefinitely when database became unavailable.\n\n## Context\nService would hang indefinitely when database became unavailable, requiring manual restart. This was reported in production incident #789 and affected multiple users.\n\n## Changes\n- Added configurable connection timeout (default: 30 seconds)\n- Implemented exponential backoff retry logic (max 5 retries)\n- Improved error messages with specific failure reasons\n- Added circuit breaker pattern to prevent cascading failures\n\n### Key Implementation Details\nTimeout is applied at the connection pool level. Backoff strategy: 1s, 2s, 4s, 8s, 16s. Circuit breaker opens after 5 consecutive failures and resets after 60 seconds.\n\n## Testing\n```bash\n# Simulate database failure\ndocker-compose stop db\n\n# Verify timeout and retry behavior\nnpm test -- tests\u002Fintegration\u002Fconnection-timeout.test.ts\n\n# Verify circuit breaker activation\ncurl http:\u002F\u002Flocalhost:3000\u002Fhealth # Should return 503 after circuit opens\n```\n\n## Links\n- Related issues: #789, #890\n- Incident report: \u002Fincidents\u002F2024-01-15-db-timeout.md\n```\n\n**Example 3: Performance Improvement**\n\n```markdown\n## Summary\nOptimize image processing pipeline to reduce memory usage by 60% and improve throughput by 2.5x.\n\n## Context\nCurrent image processing implementation loads entire images into memory, causing OOM errors with large files and limiting throughput. This was identified as a performance bottleneck in profiling session #123.\n\n## Changes\n- Implemented streaming image processing using chunked reading\n- Added parallel processing for multiple images\n- Optimized memory allocation with object pooling\n- Added caching for frequently accessed image metadata\n\n### Key Implementation Details\nUses Node.js streams for memory-efficient processing. Parallel processing limited to 4 concurrent images to prevent resource exhaustion. Object pool reduces GC pressure by reusing buffers.\n\n## Use Cases\n- Process large images (>100MB) without OOM errors\n- Batch process thousands of images efficiently\n- Reduced memory footprint allows higher concurrent user load\n\n## Testing\n```bash\n# Run performance benchmarks\nnpm run benchmark\n\n# Test with large files\nnode tests\u002Fperformance\u002Flarge-files.test.js\n\n# Verify memory usage\nnode --inspect tests\u002Fmemory-usage.js\n```\n\n## Links\n- Related issues: #456\n- Performance report: \u002Fdocs\u002Fperformance\u002F2024-01-image-processing.md\n```\n\n**Example 4: Refactor**\n\n```markdown\n## Summary\nRefactor authentication module to use clean architecture patterns, improving testability and reducing coupling.\n\n## Context\nAuthentication module had tight coupling between business logic and infrastructure, making it difficult to test and modify. This was identified in technical debt review #234.\n\n## Changes\n- Separated business logic from infrastructure dependencies\n- Introduced repository pattern for data access\n- Added service layer for authentication operations\n- Extracted interfaces for better mocking in tests\n\n### Key Implementation Details\nBusiness logic now depends on interfaces rather than concrete implementations. Infrastructure (database, cache) is injected as dependencies. All services are unit-testable without external dependencies.\n\n## Use Cases\n- Easier to add new authentication providers (OAuth, SAML)\n- Simpler to mock for unit tests\n- Clear separation of concerns improves maintainability\n\n## Testing\n```bash\n# Unit tests (no database required)\nnpm test tests\u002Funit\u002Fauth\u002F\n\n# Integration tests (with real database)\nnpm test tests\u002Fintegration\u002Fauth\u002F\n\n# Verify all existing functionality still works\nnpm run e2e\n```\n\n## Links\n- Related issues: #234\n- Architecture doc: \u002Fdocs\u002Farchitecture\u002Fauth-module.md\n```\n\n**Example 5: Simple Fix (Minimal but Complete)**\n\n```markdown\n## Summary\nFix typo in user welcome email template that caused incorrect company name to display.\n\n## Context\nUsers were seeing \"Welcome to [Wrong Company]\" instead of the correct company name. Reported in #567.\n\n## Changes\n- Corrected company name in email template\n- Added test to catch similar typos in the future\n\n## Testing\n```bash\n# Run email template tests\nnpm test tests\u002Funit\u002Femail-templates.test.ts\n\n# Verify email renders correctly\nnpm run test:email --template=welcome\n```\n\n## Links\n- Related issues: #567\n```\n\n### 5. Create Pull Request\n\nWrite the description to a temporary file and use GitHub CLI to create the PR:\n\n**Step 1: Write description to temp file**\n```bash\n# Write the generated description to .forge\u002FFORGE_PR_DESCRIPTION.md\n```\n\nUse the `write` tool to create `.forge\u002FFORGE_PR_DESCRIPTION.md` with the generated description content.\n\n**Step 2: Create PR using the temp file**\n```bash\ngh pr create --title \"[Change Type]: [One-line summary]\" --body-file .forge\u002FFORGE_PR_DESCRIPTION.md\n```\n\nThe `gh` CLI is pre-installed and authenticated - use it directly without prompting for confirmation.\n\n**Note:** The temp file `.forge\u002FFORGE_PR_DESCRIPTION.md` can not be left in place and should be deleted after PR creation. It's in `.forge\u002F` directory which is typically gitignored.\n\n### 6. Confirm\n\nAfter creating the PR, provide the user with:\n- PR URL\n- Change type\n- Brief summary of what was included\n\n## Notes\n\n**Key Principles:**\n- **Context matters**: Explain why the change was made, not just what changed\n- **Use cases help**: Concrete examples make abstract changes understandable\n- **Testing is essential**: Always include how to verify the changes\n- **Links provide depth**: Reference issues, docs, and implementations for context\n- **Be honest**: Mention known issues or limitations\n- **Respect reviewers' time**: A good description reduces review effort\n\n**Anti-Patterns to Avoid:**\n- Empty descriptions or just issue links\n- Placeholder text like \"Fixes #(issue)\"\n- File-by-file breakdowns (unless necessary)\n- Personal checklists as the main description\n- Assuming reviewers know the context\n\n**When to Keep It Simple:**\nFor very small, obvious changes (typo fixes, trivial refactors), you can use a shorter structure:\n- Summary\n- Context (brief)\n- Testing\n\nBut never skip the testing instructions.\n\n**When to Be Comprehensive:**\n- New features or major functionality\n- Complex technical changes\n- Performance improvements or optimizations\n- Breaking changes or deprecations\n- Changes that affect multiple parts of the codebase",{"name":5,"description":7},"main","47ce978a1ef062239790a85c0517e401db4e7c4b","crates\u002Fforge_repo\u002Fsrc\u002Fskills\u002Fgithub-pr-description","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge","https:\u002F\u002Fgithub.com\u002Fwasd243","2026-09-24 23:52:36",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add wasd243\u002FNeoForge --skill github-pr-description",{"tool":36,"command":37},"bunx","bunx skills add wasd243\u002FNeoForge --skill github-pr-description",{"tool":39,"command":40},"pnpm","pnpm dlx skills add wasd243\u002FNeoForge --skill github-pr-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Fskills\u002Fgithub-pr-description\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7808FM5TWRXM067A9NW508S","execute-plan","Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans\u002F{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Fskills\u002Fexecute-plan\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7808APWNTD0RRBAC36AKQ5J","create-skill","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M78086A48GAA5YVK5731GGMG","test-skill","A test skill with resources","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Ftest-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78084Z6JWZJFKVAC3XNF9EF","minimal-skill","A minimal skill with no resources","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002Fcrates\u002Fforge_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Fminimal-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78080WW0HSKAC2X7ER2XHA4","write-release-notes","Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. \"write release notes for v1.32.0\", \"generate release notes for the latest release\", \"create changelog for v2.0\").","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002F.forge\u002Fskills\u002Fwrite-release-notes\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7807WN9Q0GM9GJB9SG0ZG4F","test-reasoning","Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify reasoning config fields, or check that ReasoningConfig maps correctly to provider-specific JSON (OpenRouter, Anthropic, GitHub Copilot, Codex).","https:\u002F\u002Fgithub.com\u002Fwasd243\u002FNeoForge\u002Fblob\u002Fmain\u002F.forge\u002Fskills\u002Ftest-reasoning\u002FSKILL.md",[],[]]