fix(skills): remove phantom resource references and fix CoC links (#447)

Remove references to non-existent resource files (references/, assets/,
scripts/, examples/) from 115 skill SKILL.md files. These sections
pointed to directories and files that were never created, causing
confusion when users install skills.

Also fix broken Code of Conduct links in issue templates to use
absolute GitHub URLs instead of relative paths that 404.

plugins/framework-migration/skills/angular-migration/SKILL.md

@@ -384,32 +384,3 @@ Phase 4: Cleanup (1-2 weeks)
 - Optimize bundle
 - Final testing
 ```
-
-## Resources
-
-- **references/hybrid-mode.md**: Hybrid app patterns
-- **references/component-migration.md**: Component conversion guide
-- **references/dependency-injection.md**: DI migration strategies
-- **references/routing.md**: Routing migration
-- **assets/hybrid-bootstrap.ts**: Hybrid app template
-- **assets/migration-timeline.md**: Project planning
-- **scripts/analyze-angular-app.sh**: App analysis script
-
-## Best Practices
-
-1. **Start with Services**: Migrate services first (easier)
-2. **Incremental Approach**: Feature-by-feature migration
-3. **Test Continuously**: Test at every step
-4. **Use TypeScript**: Migrate to TypeScript early
-5. **Follow Style Guide**: Angular style guide from day 1
-6. **Optimize Later**: Get it working, then optimize
-7. **Document**: Keep migration notes
-
-## Common Pitfalls
-
-- Not setting up hybrid app correctly
-- Migrating UI before logic
-- Ignoring change detection differences
-- Not handling scope properly
-- Mixing patterns (AngularJS + Angular)
-- Inadequate testing

plugins/framework-migration/skills/database-migration/SKILL.md

@@ -401,33 +401,3 @@ module.exports = {
   },
 };
 ```
-
-## Resources
-
-- **references/orm-switching.md**: ORM migration guides
-- **references/schema-migration.md**: Schema transformation patterns
-- **references/data-transformation.md**: Data migration scripts
-- **references/rollback-strategies.md**: Rollback procedures
-- **assets/schema-migration-template.sql**: SQL migration templates
-- **assets/data-migration-script.py**: Data migration utilities
-- **scripts/test-migration.sh**: Migration testing script
-
-## Best Practices
-
-1. **Always Provide Rollback**: Every up() needs a down()
-2. **Test Migrations**: Test on staging first
-3. **Use Transactions**: Atomic migrations when possible
-4. **Backup First**: Always backup before migration
-5. **Small Changes**: Break into small, incremental steps
-6. **Monitor**: Watch for errors during deployment
-7. **Document**: Explain why and how
-8. **Idempotent**: Migrations should be rerunnable
-
-## Common Pitfalls
-
-- Not testing rollback procedures
-- Making breaking changes without downtime strategy
-- Forgetting to handle NULL values
-- Not considering index performance
-- Ignoring foreign key constraints
-- Migrating too much data at once

plugins/framework-migration/skills/dependency-upgrade/SKILL.md

@@ -366,64 +366,3 @@ npm install --workspaces
 # Update specific workspace
 npm install package@latest --workspace=packages/app
 ```
-
-## Resources
-
-- **references/semver.md**: Semantic versioning guide
-- **references/compatibility-matrix.md**: Common compatibility issues
-- **references/staged-upgrades.md**: Incremental upgrade strategies
-- **references/testing-strategy.md**: Comprehensive testing approaches
-- **assets/upgrade-checklist.md**: Step-by-step checklist
-- **assets/compatibility-matrix.csv**: Version compatibility table
-- **scripts/audit-dependencies.sh**: Dependency audit script
-
-## Best Practices
-
-1. **Read Changelogs**: Understand what changed
-2. **Upgrade Incrementally**: One major version at a time
-3. **Test Thoroughly**: Unit, integration, E2E tests
-4. **Check Peer Dependencies**: Resolve conflicts early
-5. **Use Lock Files**: Ensure reproducible installs
-6. **Automate Updates**: Use Renovate or Dependabot
-7. **Monitor**: Watch for runtime errors post-upgrade
-8. **Document**: Keep upgrade notes
-
-## Upgrade Checklist
-
-```markdown
-Pre-Upgrade:
-
-- [ ] Review current dependency versions
-- [ ] Read changelogs for breaking changes
-- [ ] Create feature branch
-- [ ] Backup current state (git tag)
-- [ ] Run full test suite (baseline)
-
-During Upgrade:
-
-- [ ] Upgrade one dependency at a time
-- [ ] Update peer dependencies
-- [ ] Fix TypeScript errors
-- [ ] Update tests if needed
-- [ ] Run test suite after each upgrade
-- [ ] Check bundle size impact
-
-Post-Upgrade:
-
-- [ ] Full regression testing
-- [ ] Performance testing
-- [ ] Update documentation
-- [ ] Deploy to staging
-- [ ] Monitor for errors
-- [ ] Deploy to production
-```
-
-## Common Pitfalls
-
-- Upgrading all dependencies at once
-- Not testing after each upgrade
-- Ignoring peer dependency warnings
-- Forgetting to update lock file
-- Not reading breaking change notes
-- Skipping major versions
-- Not having rollback plan

plugins/framework-migration/skills/react-modernization/SKILL.md

@@ -495,32 +495,3 @@ function List<T>({ items, renderItem }: ListProps<T>) {
 - [ ] Check for warnings in console
 - [ ] Performance testing
 ```
-
-## Resources
-
-- **references/breaking-changes.md**: Version-specific breaking changes
-- **references/codemods.md**: Codemod usage guide
-- **references/hooks-migration.md**: Comprehensive hooks patterns
-- **references/concurrent-features.md**: React 18 concurrent features
-- **assets/codemod-config.json**: Codemod configurations
-- **assets/migration-checklist.md**: Step-by-step checklist
-- **scripts/apply-codemods.sh**: Automated codemod script
-
-## Best Practices
-
-1. **Incremental Migration**: Don't migrate everything at once
-2. **Test Thoroughly**: Comprehensive testing at each step
-3. **Use Codemods**: Automate repetitive transformations
-4. **Start Simple**: Begin with leaf components
-5. **Leverage StrictMode**: Catch issues early
-6. **Monitor Performance**: Measure before and after
-7. **Document Changes**: Keep migration log
-
-## Common Pitfalls
-
-- Forgetting useEffect dependencies
-- Over-using useMemo/useCallback
-- Not handling cleanup in useEffect
-- Mixing class and functional patterns
-- Ignoring StrictMode warnings
-- Breaking change assumptions