基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/cxcscmu/SkillLearnBench --skill git-patch-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Handles reading, populating, and saving .docx files using the python-docx library. Use this skill for any tasks involving template filling or modifying Word documents.
Perform various data analysis on SEC 13-F and obtain some insights of fund activities such as number of holdings, AUM, and change of holdings between two quarters.
This skill includes search capability in 13F, such as fuzzy search a fund information using possibly inaccurate name, or fuzzy search a stock cusip info using its name.
| name | git-patch-workflow |
| description | Creating, managing, and applying unified diff patches with Git for source code modifications. |
cd /path/to/repo
git diff path/to/file.java > /path/to/patch/fix.patch
git diff --cached > /path/to/patch/fix.patch
# Create patch from last N commits
git format-patch -N HEAD
# Create patch from specific commit
git show COMMIT_HASH > /path/to/patch/fix.patch
A unified diff patch looks like:
--- a/original/path/file.java
+++ b/modified/path/file.java
@@ -10,5 +10,6 @@ class MyClass {
// context line
- old code here
+ new code here
// context line
Key components:
--- prefix: original file+++ prefix: modified file@@ markers: line numbers and context- prefix: removed lines+ prefix: added linescd /path/to/repo
patch -p1 < /path/to/patch/fix.patch
# Dry-run to test application
patch -p1 --dry-run < /path/to/patch/fix.patch
# Apply with strict checking
patch -p1 < /path/to/patch/fix.patch
# Apply with less strict checking
patch -p0 < /path/to/patch/fix.patch
git diff or git format-patch for consistencyfix-javascript-security-bypass.patch)# Check if patch was applied
git status
git diff HEAD
# Verify specific file was patched
git show HEAD:path/to/file.java | grep "your fix"
For multiple related patches:
# Create patches in order
git diff HEAD~2 HEAD~1 > patch1.patch
git diff HEAD~1 HEAD > patch2.patch
# Apply in sequence
patch -p1 < patch1.patch
patch -p1 < patch2.patch