[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74AWW1P932KXT4WGNES49YP":3,"skill-same:01M74AWW1P932KXT4WGNES49YP":56},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M74AWW1P932KXT4WGNES49YP","column-renames-metadata-only",null,"Column Renames (Metadata-Only)","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcolumn-renames-metadata-only\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: column-renames-metadata-only\ndescription: \"Column Renames (Metadata-Only)\"\nmetadata:\n  short-description: \"Column Renames (Metadata-Only)\"\n  original-index: 05\n---\n\n# Column Renames (Metadata-Only)\n\n## What\n\nPostgreSQL's `ALTER TABLE RENAME COLUMN` is a **metadata-only** operation. It\nchanges the column name in the system catalogs (`pg_attribute`) without touching\nthe actual table data. It's instant regardless of table size.\n\n## Why\n\nThis matters because renaming a column on a 100-million-row table takes the\nsame time as renaming one on a 10-row table: effectively zero. No table rewrite,\nno data movement, no downtime.\n\n## How\n\n```sql\nALTER TABLE public.\"Applicant\"\n    RENAME COLUMN \"SpeialtyRequirement\" TO \"SpecialtyRequirement\";\n```\n\nWhat happens internally:\n1. PostgreSQL acquires an `ACCESS EXCLUSIVE` lock on the table (very briefly)\n   -- this is the strictest lock mode but the hold time is sub-millisecond\n   since only catalog metadata is updated (PG 16 docs: sql-altertable.html)\n2. Updates `pg_attribute.attname` for that column's OID\n3. Releases the lock\n\nTotal time: typically \u003C 1ms.\n\n## What It Does NOT Do\n\n- Does NOT update stored procedures that reference the old column name\n- Does NOT update views that reference the old column name\n- Does NOT update application code\n- Does NOT update indexes (indexes reference column attnum, not name)\n- Does NOT change parameter names in function signatures\n\nThis is why  had to separately update 4 stored procedures -- the column\nrename alone would have left them broken with `\"column does not exist\"` errors.\n\n## When to Use\n\n- Fixing typos in column names\n- Standardizing naming conventions\n- Any rename where you can also update all dependent objects\n\n## Where We Used It\n\n- ****: Renamed 4 misspelled columns in `public.\"Applicant\"`\n  - `SpeialtyRequirement` -> `SpecialtyRequirement`\n  - `AddionalCommentsAuthToWork` -> `AdditionalCommentsAuthToWork`\n  - `AdditinalCpmmentsUnderAge` -> `AdditionalCommentsUnderAge`\n  - `VertirnaryTechOrAssistant` -> `the clientTechOrAssistant`\n\n## Related Skills\n\n- **Skill #06** (pg_get_functiondef) -- update procedures after column renames\n- **Skill #08** (Deep Grep) -- verify all references found\n- **Skill #14** (Research Checklist) -- find all affected objects before renaming\n- **Skill #19** (Multi-Object Rename) -- when the rename includes the table itself\n\n## Gotchas\n\n- **Stored procedures break** if they use quoted column names (`\"OldName\"`)\n- **Views break** if they reference the old column name\n- **Application code breaks** if it uses the old column name in queries\n- Always search for ALL dependent objects before renaming\n\n---\n\n*Category: DDL | Origin: *\n","# Column Renames (Metadata-Only)\n\n## What\n\nPostgreSQL's `ALTER TABLE RENAME COLUMN` is a **metadata-only** operation. It\nchanges the column name in the system catalogs (`pg_attribute`) without touching\nthe actual table data. It's instant regardless of table size.\n\n## Why\n\nThis matters because renaming a column on a 100-million-row table takes the\nsame time as renaming one on a 10-row table: effectively zero. No table rewrite,\nno data movement, no downtime.\n\n## How\n\n```sql\nALTER TABLE public.\"Applicant\"\n    RENAME COLUMN \"SpeialtyRequirement\" TO \"SpecialtyRequirement\";\n```\n\nWhat happens internally:\n1. PostgreSQL acquires an `ACCESS EXCLUSIVE` lock on the table (very briefly)\n   -- this is the strictest lock mode but the hold time is sub-millisecond\n   since only catalog metadata is updated (PG 16 docs: sql-altertable.html)\n2. Updates `pg_attribute.attname` for that column's OID\n3. Releases the lock\n\nTotal time: typically \u003C 1ms.\n\n## What It Does NOT Do\n\n- Does NOT update stored procedures that reference the old column name\n- Does NOT update views that reference the old column name\n- Does NOT update application code\n- Does NOT update indexes (indexes reference column attnum, not name)\n- Does NOT change parameter names in function signatures\n\nThis is why  had to separately update 4 stored procedures -- the column\nrename alone would have left them broken with `\"column does not exist\"` errors.\n\n## When to Use\n\n- Fixing typos in column names\n- Standardizing naming conventions\n- Any rename where you can also update all dependent objects\n\n## Where We Used It\n\n- ****: Renamed 4 misspelled columns in `public.\"Applicant\"`\n  - `SpeialtyRequirement` -> `SpecialtyRequirement`\n  - `AddionalCommentsAuthToWork` -> `AdditionalCommentsAuthToWork`\n  - `AdditinalCpmmentsUnderAge` -> `AdditionalCommentsUnderAge`\n  - `VertirnaryTechOrAssistant` -> `the clientTechOrAssistant`\n\n## Related Skills\n\n- **Skill #06** (pg_get_functiondef) -- update procedures after column renames\n- **Skill #08** (Deep Grep) -- verify all references found\n- **Skill #14** (Research Checklist) -- find all affected objects before renaming\n- **Skill #19** (Multi-Object Rename) -- when the rename includes the table itself\n\n## Gotchas\n\n- **Stored procedures break** if they use quoted column names (`\"OldName\"`)\n- **Views break** if they reference the old column name\n- **Application code breaks** if it uses the old column name in queries\n- Always search for ALL dependent objects before renaming\n\n---\n\n*Category: DDL | Origin: *\n",{"name":5,"metadata":24,"description":7},{"original-index":25,"short-description":7},5,"master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fcolumn-renames-metadata-only",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add CarlosCaPe\u002Foctorato --skill column-renames-metadata-only",{"tool":42,"command":43},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill column-renames-metadata-only",{"tool":45,"command":46},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill column-renames-metadata-only","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcolumn-renames-metadata-only\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"skill.json","REFERENCE","参考文档",157,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcolumn-renames-metadata-only\u002Fskill.json",[57,66,74,81,89,97],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\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":61,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]