Skip to main content
تشغيل أي مهارة في Manus
بنقرة واحدة
Fizzizist
ملف منشئ GitHub

Fizzizist

عرض على مستوى المستودعات لـ 13 skills مجمعة عبر 2 مستودعات GitHub.

skills مجمعة
13
مستودعات
2
محدث
2026-06-16
مستكشف المستودعات

المستودعات و skills الممثلة

mach6-implement
مطوّرو البرمجيات

Implement a plan from a PR, or fix review findings / CI failures. Usage: mach6-implement 42 [finding-numbers] or mach6-implement 42 ci

2026-05-13
mach6-publish
مطوّرو البرمجيات

Pre-merge checks, version bump, merge PR, git tag, GitHub release. Version bump happens BEFORE merge (on the feature branch) because master requires PRs. Usage: mach6-publish 42

2026-05-13
mach6-review
محللو ضمان جودة البرمجيات والمختبرون

Run specialized review agents in parallel on a PR (code-reviewer, error-auditor, test-reviewer, completeness-checker, simplifier), post findings, then independently assess each finding to separate genuine issues from nitpicks and false positives. Usage: mach6-review 42 [aspects]

2026-05-13
mach6-issue
مطوّرو البرمجيات

Assess an existing GitHub issue (explore codebase, identify scope/risks/ambiguities, post assessment) or create a new structured issue. Usage: mach6-issue 42 (assess) or mach6-issue (create) or mach6-issue <description> (create with context)

2026-04-23
mach6-plan
مطوّرو البرمجيات

Explore codebase, create implementation plan, create feature branch with dummy commit, open draft PR, post plan as PR comment. Everything lives on the PR from this point forward. Usage: mach6-plan 42

2026-04-23
mach6-push
مطوّرو البرمجيات

Commit changes, push to remote, and post a progress comment on the associated PR or issue. Stages files by name (never git add -A), matches existing commit style, auto-detects PR from branch. Usage: mach6-push [optional commit message]

2026-04-23
code-review
محللو ضمان جودة البرمجيات والمختبرون

Review code changes, provide feedback, and suggest improvements.

2026-03-27
dg-publish
مطوّرو البرمجيات

Pre-merge checks, version bump, create PR/MR. Version bump happens BEFORE merge (on the feature branch) because master requires PRs. Usage: dg-publish

2026-06-16
dg-issue
مطوّرو البرمجيات

Assess an existing doppelganger issue (explore codebase, identify scope/risks/ambiguities, post assessment) or create a new structured issue. Usage: dg-issue 42 (assess) or dg-issue (create) or dg-issue <description> (create with context)

2026-06-12
dg-plan
مطوّرو البرمجيات

Explore codebase, create implementation plan, create feature branch, create doppelganger(dg) branch, post plan as dg branch comment. Everything lives on the dg branch from this point forward. Usage: dg-plan 42

2026-06-12
dg-commit
مطوّرو البرمجيات

Commit changes, and post a progress comment in doppelganger(dg). Stages files by name (never git add -A), matches existing commit style. Usage: dg-commit [optional commit message]

2026-06-12
dg-review
محللو ضمان جودة البرمجيات والمختبرون

Run specialized review agents in parallel on a doppelganger(dg) branch (code-reviewer, error-auditor, test-reviewer, completeness-checker, simplifier), write findings, then independently assess each finding to separate genuine issues from nitpicks and false positives. Usage: dg-review [aspects]

2026-06-12
dg-implement
مطوّرو البرمجيات

Implement a plan from a doppelganger(dg) branch, or fix review findings. Usage: dg-implement [finding-numbers]

2026-06-12
عرض 2 من أصل 2 مستودعات
تم تحميل كل المستودعات