القائمة
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.
Orchestrated GitHub PR review skill. Use when the user provides a PR link or asks for a senior, blocker-focused pull request review with Jira acceptance, tests, docs, security, architecture, memory, and copy/paste GitHub markdown comments.
| name | commitall |
| description | Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing. |
Commit all local changes in this repository in logical, cohesive groups until the working tree is clean.
Run these first:
git status --shortgit diff --statgit diff --staged --statgit log --oneline -12git branch --show-currentTreat these as out of scope unless the user explicitly asks for them:
.pr-body.mdstgcore-app-ulpDo not edit, stage, commit, or mention them as work to clean up. Do not add them to .gitignore.
Extract a Jira key from the current branch name.
Accepted examples:
feature/FLYWL-1234bugfix/FLYWL-1234-somethingFLYWL-1234/fooIf a Jira key is present, every commit message in this run must start with:
FLYWL-1234: If no Jira key is present, stop and ask the user for the Jira key before committing.
Keep the rest of each message concise and explain why that grouped change exists.
git add <paths>git status --short after each commit.Do not mix unrelated files into one commit just to get clean faster.
--no-verify..env, credentials, or tokens.stgcore-app-ulp unless explicitly requested.When done, print:
git status --shortThe final status should be clean aside from the explicitly ignored items if they still exist.