القائمة
OpenAgentd workflow for well-formatted, detailed conventional commits.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/lthoangg/OpenAgentd --skill oad-commitيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Update or upgrade the agent's own configuration on request — swap the model, add tools or MCP servers, change the image-generation provider/model, or install a new skill. Use when the user says things like "upgrade yourself", "switch your model to X", "use Gemini for images", "make yourself faster/smarter".
OpenAgentd testing reference — environment setup, run commands, and fix patterns for backend (pytest) and frontend (Bun/RTL). Load this for running, fixing, or adding coverage to existing tests. For writing a failing test before new code, use oad/test-driven-development instead.
OpenAgentd workflow for investigating bugs, regressions, sessions, and runtime issues.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | oad/commit |
| description | OpenAgentd workflow for well-formatted, detailed conventional commits. |
Git Commit Execution Workflow
git status --porcelain. If no files are staged, execute git add ..git diff --cached to evaluate the technical scope and architectural impact (e.g., DDD shifts or C4 updates).oad/docs to sync any documentation affected by the staged changes.<type>: <subject>git commit -m "<message>" and output the commit hash and a brief summary.Note: Multiple commits are preferred for large changes. If the scope is too broad, break it down into smaller, focused commits following the same workflow (do not force to have multiple commits if the change is small and cohesive).
Sizing: target ~100 changed lines per commit (a single logical, self-contained change); ~300 is acceptable for one cohesive change; ~1000+ should be split. Keep refactors and behavior changes in separate commits — mixing "renamed X" with "fixed Y" makes both harder to review and revert.
Commit Conventions
| Category | Type |
|---|---|
| Features | feat |
| Fixes | fix |
| Refactor | refactor |
| Maintenance | chore/docs |
| Style | style |