القائمة
Delta integration for viewing diffs in the terminal. Use when showing file differences to the user with syntax highlighting via delta.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | delta |
| description | Delta integration for viewing diffs in the terminal. Use when showing file differences to the user with syntax highlighting via delta. |
Tools for viewing diffs with syntax highlighting using delta.
delta must be installed and available in PATH (delta --version to verify).
delta <file1> <file2>
git diff HEAD -- path/to/file | delta
git diff -- path/to/file | delta
git diff --cached HEAD -- path/to/file | delta
git diff <commit1> <commit2> -- path/to/file | delta
git diff HEAD~1 HEAD -- path/to/file | delta
git show <commit> -- path/to/file | delta
git show HEAD~1:path/to/file > /tmp/old
delta /tmp/old path/to/file
--side-by-side — side-by-side view--line-numbers — show line numbers--diff-highlight — highlight changed words within lines--no-gitconfig — ignore local git config (use delta defaults)Example:
git diff HEAD -- path/to/file | delta --side-by-side --line-numbers
delta reads from stdin, so always pipe git output to itgit log --oneline -5 -- path/to/file to verify file has history before diffingcore.pager = delta), plain git diff already uses itTop-level session orchestration rules — subagent routing, context hygiene, and implementation discipline. Not intended for subagents.
Wrike connector skill for managing Agile work items (Epics, Stories, Tasks, sub-tasks, comments, and attachments) via the Wrike REST API v4. Use this skill whenever an agent needs to read or write Wrike workspace data.
Post-merge integrity check skill for SugarCRM projects. Use whenever an agent needs to compare two branches after a version-upgrade merge, detect lost or damaged custom code (identified by CUSTOM_MARKERS), and generate git patches for CRITICAL/HIGH findings.
Browser automation skill for testing SugarCRM Enterprise (v12-25). Use for simulating user interactions: clicking buttons, filling forms, navigating modules, creating records, and verifying functionality. Requires Playwright and Chromium browser installed.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs.