القائمة
Stage and commit the current working tree changes with a well-formed commit message. Use when the user says "commit", "git commit", "commit my changes", or invokes /git-commit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Facilitate a structured feature brainstorming session for the personal finance app. Use this skill when the user wants to explore a new feature idea, plan what to build next, or think through a product direction. Triggers on phrases like "brainstorm", "let's think about", "what should we build", "plan a feature", or "I have an idea".
Fetch ALL pending [Feature] Asana tasks and drive them through implementation with maximum safe parallelism. Use this when the user wants to drain the entire feature backlog in one command rather than processing tasks one at a time. Triggers on "process the backlog", "drain the backlog", "build everything in Asana", or explicit /process-backlog invocation.
Drive new Java feature development using red-green-refactor TDD. Use when asked to "add a feature TDD", "write the test first", "do TDD for X", or "red-green-refactor X". Takes a feature description and iterates: failing test → minimal implementation → refactor.
Build and run the team-tom Java Maven app. Use when asked to "run the app", "start the budget tracker", "demo the app", or "run java". Compiles with Maven, then launches the jar.
This skill should be used when the user or an agent asks to "implement a task", "execute a dev task", "code the task", "write the code for a task", "pick up a task from the orchestrator", or when a task file needs to be implemented. Reads a structured task specification file written by an orchestrator agent and produces working code in the target programming language.
This skill should be used when the user asks to "orchestrate tasks", "break down a feature", "plan the work", "create tasks for the developer agent", "assign tasks", "decompose the requirement", or "set up the task queue". Takes a high-level requirement, explores the codebase, breaks the work into discrete coding tasks, writes task files to .claude/tasks/, and hands them off to the dev-coder skill one at a time.
| name | git-commit |
| description | Stage and commit the current working tree changes with a well-formed commit message. Use when the user says "commit", "git commit", "commit my changes", or invokes /git-commit. |
| version | 1.0.0 |
Stages changes and creates a git commit with a clear, descriptive message.
Run these in parallel:
git status — identify modified, untracked, and deleted files.git diff — read the full diff of unstaged changes.git diff --cached — read the full diff of already-staged changes.git log --oneline -5 — read recent commit messages to match style.$ARGUMENTS names specific files or paths, stage only those.git add -u) plus any new files that are clearly part of the current work (use judgement — do NOT stage .env, credential files, large binaries, or build artefacts such as target/, dist/, node_modules/).Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>Run git commit -m "$(cat <<'EOF'\n<message>\nEOF\n)" (or PowerShell equivalent) using the drafted message. Pass the full message via heredoc to avoid shell escaping issues.
Run git log --oneline -1 and report the new commit hash and subject line to the user.
--no-verify)..env, secrets, or build artefacts.