تشغيل أي مهارة في Manus بنقرة واحدة

$pwd:

smart-commits

Name: Smart Commits
Author: hoangnb24

// Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.

تشغيل في Manus

$ git log --oneline --stat

stars:٢١٨

forks:٦٦

updated:٢٠ مايو ٢٠٢٦ في ١٥:٣١

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	smart-commits
description	Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.
metadata	{"dependencies":{"git-cli":{"kind":"command","command":"git","missing_effect":"unavailable","reason":"The skill inspects repository changes, creates commits, and pushes through git."}}}

Smart Commits

Turn the current working tree into one or more coherent commits, then push when the repository has a configured remote. This skill is for committing existing work. It must not become a feature-editing session.

Core Rules

Never edit product code or docs just to make a commit easier. If validation exposes a real blocker, report it and keep the working tree intact unless the user explicitly asks for a fix.
Never stash, reset, checkout away, overwrite, or revert unrelated changes. In multi-agent repos, treat every existing change as intentional work unless the user explicitly asks otherwise.
Preserve the user's requested boundary. If they say to leave a path, topic, or change set alone, do not stage it.
Stage exact files or hunks intentionally. Avoid git add . unless the whole tree has been inspected and belongs in one commit group.
Prefer conventional commit messages with a useful body explaining why the group belongs together.
Push after committing when a remote/upstream exists. If no push destination exists, leave the commits local and say so.

Workflow

Inspect the repository:

git status --porcelain=v1
git branch --show-current
git remote -v
git diff --stat
git diff --cached --stat

Read enough representative diffs and files to understand intent. Include staged, unstaged, untracked, deleted, and renamed files.
Identify commit groups by product intent, not by file type:
- foundational/configuration changes before dependent feature changes
- source and directly coupled tests together when they prove one behavior
- docs as a separate commit only when they are independently meaningful
- generated artifacts only when they are part of the requested deliverable
Run appropriate quality gates before committing when code changed. Use the repo's own checks first. If checks are unavailable, expensive, or already known broken, record that in the final response.

Commit one group at a time:

git add <specific files>
git commit -m "<type>(<scope>): <subject>" -m "<body>"

After each commit, re-run git status --porcelain=v1 and continue until all in-scope changes are committed.
Push:
```
git push
```
If the branch lacks an upstream, use git push -u origin <branch> only when the remote and branch name are clearly correct.

Grouping Guidance

Good groups:

refactor(auth): extract token validation helper
feat(users): add email verification endpoint
test(users): cover email verification flow

Bad groups:

chore: update files
docs: update docs and app code
test: update tests when the tests prove multiple unrelated features

Final Response

Report the commits created, push result, validation run, and any remaining out-of-scope or uncommitted files. If the tree is already clean when invoked, verify the latest relevant commit and say no new commit was needed.

related-skills.json

نفس المستودع

using-khuym.md

from "hoangnb24/skills"

Use when starting or resuming any Khuym project session, choosing the next Khuym skill, running go mode, checking onboarding/scout state, or enforcing workflow gates. Bootstrap meta-skill for routing across the Khuym agentic development ecosystem.

2026-05-20218

goal-griller.md

from "hoangnb24/skills"

Use when the user wants to turn a rough idea, vague task, feature wish, bug-fix intent, or Codex /goal objective into a clear verifiable goal prompt. Use when the user mentions goal mode, /goal, set_goal, long-running autonomous Codex work, or asks to be interviewed/grilled before creating a goal.

2026-05-18218

visual-learner.md

from "hoangnb24/skills"

Create self-contained interactive HTML visual explainers that turn difficult topics, concepts, code, math, systems, or arguments into memorable explorable artifacts. Use when Codex should research a topic, choose an interaction model, and build an artifact with simulations, diagrams, charts, sliders, hover inspection, scrollytelling, or small game mechanics so readers can explore and understand the message.

2026-05-18218

concept-game-builder.md

from "hoangnb24/skills"

Use when Codex should turn a concept, topic, tutorial, lesson, algorithm, system, workflow, or abstract idea into a playable browser game that teaches through interaction. Use for planning or implementing educational web games with the Game Studio plugin, including concept-to-mechanic translation, gameplay loop design, learning progression, and browser-game QA.

2026-05-18218

planning.md

from "hoangnb24/skills"

Use when exploring has locked CONTEXT.md and the work needs planning before validation.

2026-05-03218

validating.md

from "hoangnb24/skills"

Use when planning has an approved work shape and needs feasibility validation before swarming.

2026-05-03218

package.json

"author": "hoangnb24"

"repository": "hoangnb24/skills"

فتح مستودع GitHub عرض مستودعات المنشئ

$ install --global

$ download --local

تشغيل في Manus

$ useful --forSOC

مطوّرو البرمجياتمهن الحاسوب والرياضيات15-1252L4

Smart Commits

Core Rules

Never edit product code or docs just to make a commit easier. If validation exposes a real blocker, report it and keep the working tree intact unless the user explicitly asks for a fix.

Never stash, reset, checkout away, overwrite, or revert unrelated changes. In multi-agent repos, treat every existing change as intentional work unless the user explicitly asks otherwise.

Preserve the user's requested boundary. If they say to leave a path, topic, or change set alone, do not stage it.

Stage exact files or hunks intentionally. Avoid git add . unless the whole tree has been inspected and belongs in one commit group.

Prefer conventional commit messages with a useful body explaining why the group belongs together.

Push after committing when a remote/upstream exists. If no push destination exists, leave the commits local and say so.

Workflow

Inspect the repository:

git status --porcelain=v1
git branch --show-current
git remote -v
git diff --stat
git diff --cached --stat

Read enough representative diffs and files to understand intent. Include staged, unstaged, untracked, deleted, and renamed files.

Identify commit groups by product intent, not by file type:

foundational/configuration changes before dependent feature changes
source and directly coupled tests together when they prove one behavior
docs as a separate commit only when they are independently meaningful
generated artifacts only when they are part of the requested deliverable

Run appropriate quality gates before committing when code changed. Use the repo's own checks first. If checks are unavailable, expensive, or already known broken, record that in the final response.

Commit one group at a time:

git add <specific files>
git commit -m "<type>(<scope>): <subject>" -m "<body>"

After each commit, re-run git status --porcelain=v1 and continue until all in-scope changes are committed.

Push:

git push

If the branch lacks an upstream, use git push -u origin <branch> only when the remote and branch name are clearly correct.

Grouping Guidance

Good groups:

refactor(auth): extract token validation helper

feat(users): add email verification endpoint

test(users): cover email verification flow

Bad groups:

chore: update files

docs: update docs and app code

test: update tests when the tests prove multiple unrelated features

Final Response

smart-commits

Smart Commits

Core Rules

Workflow

Grouping Guidance

Final Response

المزيد من هذا المستودع

المزيد من هذا المستودع

Smart Commits

Core Rules

Workflow

Grouping Guidance

Final Response