القائمة
Stage and commit changes with a structured, conventional commit message. Reads git diff to summarize what changed. Developer confirms message before committing. Appends to implementation log.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | 3-commit |
| description | Stage and commit changes with a structured, conventional commit message. Reads git diff to summarize what changed. Developer confirms message before committing. Appends to implementation log. |
| invoke | commit |
Stage and commit the current changes with a well-formed commit message, then record it in the implementation log.
Questions: Use the
ask_user_questiontool for every question in this skill. Never write question lists as plain text.
Run:
git status — see what's staged, unstaged, untrackedgit diff — read unstaged changesgit diff --cached — read staged changesIf there are untracked or unstaged files, ask:
These files are not staged. Include any of them?
Before drafting the message, scan for ideaLog entries that cover this work:
.pi/agent-docs/implementation-log/ for today's date (YYYY/MM/YYYY-MM-DD.ideaLog.md) and the previous 2 daysRefs: in the commit bodyIf no ideaLog files exist or none are relevant, skip silently.
Analyze the diff and draft a conventional commit message:
<type>(<scope>): <short summary>
<body — only if the why is non-obvious>
Refs: <relative path to ideaLog file(s)>
Types: feat, fix, chore, refactor, docs, test, perf, style, ci
Scope: the app/package name (monorepos) or module name (single-package)
Rules:
Refs: line when relevant ideaLog(s) found in Step 3 — path relative to repo rootNo project-specific commit conventions yet. sync-spec will populate this as patterns are learned.
Show the drafted message and ask:
Commit message:
<message>Confirm, edit, or cancel?
On confirmation:
git add <approved files>
git commit -m "<message>"
Report the commit hash and summary on success.
After a successful commit, append to .pi/agent-docs/implementation-log/YYYY/MM/YYYY-MM-DD.commit.md:
## <HH:MM> — <commit hash short> — <summary line>
<body if present>
Files: <comma-separated list of changed files>
Create the file and directory if they don't exist. Never overwrite — always append.
If .pi/agent-docs/ does not exist, skip this step silently.
If turbo.json or pnpm-workspace.yaml is detected, or if the project's tech-stack.md identifies a monorepo, use the app/package name as scope:
feat(app): add user profile page
fix(api): handle null user in session middleware
chore(packages/ui): update button variants
For non-Node monorepos (Go workspaces, Rust workspaces, Python monorepos), use the module/crate/package name as scope.
git add . or git add -A without showing the developer what will be staged.env files, secrets, or large binariesUse this skill when the user wants to save, update, or reference visual design assets for the project. Triggers on "save design", "update designs", "sync designs", "add visual", "design assets", "claude design export", "design folder", "/design". Also fires proactively when the agent is about to write UI code (React components, CSS, Tailwind classes, layout) — in that case, read the active design first so code matches the visual spec. The design folder is always at `.pi/design/` and the agent should always check it before writing any UI-facing code.
Pointer to the jsdoc-conventions standards file. Read this before writing or editing any JSDoc in a project.
Pointer to the spec-structure standards file. Read this before writing or editing any implementation spec.
Port new paradigms from the global base harness (~/.pi/agent/) into the current project's .pi/ harness, adapting them to match the project's stack, workflow tier, and conventions. Run in any project to pull in improvements made to another project's harness.
Break down a spec.md or requirements.md into an actionable tasks.md with strategic grouping and ordering. Used after spec creation and before implementation.
Detect the project type from code signals and reorganize standards folders to match — web app, backend API, CLI, library, dotfiles, mobile, or monorepo.