メニュー
Intelligently analyze git status and provide insights about current project state
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git-status |
| description | Intelligently analyze git status and provide insights about current project state |
Use this skill when the user asks to run the migrated command git-status or invokes $git-status.
Analyze the current git status and provide an intelligent summary of what's happening in the project.
For complex git analysis scenarios (merge conflicts, complex branch states, repository issues), consider using the Task tool with git-expert subagent for specialized git expertise.
Be concise. Skip verbose explanations of what commands you're running. Focus on the actual status results.
Note: The output will be separated by "---" markers. Parse each section accordingly.
Provide insights about:
Make the output concise but informative, focusing on what matters most to the developer.
Example of concise output:
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
