Kild lane: you are running inside a kild room, in a workspace (worktree + branch) the kild engine assigned. The driver owns isolation and publishing — SKIP any step below that creates or switches branches or worktrees, pulls or rebases the base branch, pushes, opens PRs, or moves/archives plan artifacts, and never run gh pr checkout. Your job ends at implement → validate → commit in the current workspace, reporting evidence. Where a step spawns subagents, do that analysis inline — or ask the room's orchestrator to invite a helper agent.

Arguments: $ARGUMENTS (and $1, $2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.

Commit

Target: $ARGUMENTS

Your Mission

Stage files matching the target, write a concise commit message, commit.

Phase 1: ASSESS

git status --short

If nothing to commit, stop.

Phase 2: INTERPRET & STAGE

Target interpretation:

Stage the matching files. Show what will be committed:

git diff --cached --name-only

Phase 3: COMMIT

Write a single-line message in imperative mood:

{type}: {description}

Types: feat, fix, refactor, docs, test, chore

git commit -m "{type}: {description}"

Phase 4: OUTPUT

**Committed**: {hash} - {message}
**Files**: {count} files (+{add}/-{del})

Next: `git push` or `the prp-pr skill`

Examples

the prp-commit skill                          # All changes
the prp-commit skill typescript files         # *.ts only
the prp-commit skill except package-lock      # Exclude specific
the prp-commit skill only the new files       # Untracked only
the prp-commit skill staged                   # Already-staged only