원클릭으로
commit
// Stage all changes and commit with appropriate message, showing changed files and edits. Use when you need to create a git commit.
// Stage all changes and commit with appropriate message, showing changed files and edits. Use when you need to create a git commit.
| name | commit |
| description | Stage all changes and commit with appropriate message, showing changed files and edits. Use when you need to create a git commit. |
Automatically stage all changes and commit with an appropriate message based on the changes made. Shows a summary of what files were changed and how.
Show current status before staging:
git status --porcelain
Stage all changes:
git add .
Get changed files for analysis:
git diff --cached --name-only
Get detailed change summary:
git diff --cached --stat
Analyze changes to create commit message:
specs/ directory that might be related to these changesfeat: add new featurefix: resolve bug in componentrefactor: reorganize utility functionsdocs: update documentationchore: update dependenciesCommit the changes:
git commit -m "Generated commit message"
Show commit summary:
git show --stat --oneline HEAD
type: descriptionspecs/ indicate major featuresFiles staged for commit:
M apps/web/src/components/TaskList.tsx
A specs/task-filters.md
M packages/ui/src/Button.tsx
D apps/web/src/old-component.tsx
Changes summary:
apps/web/src/components/TaskList.tsx | 15 ++++++++++++---
specs/task-filters.md | 42 +++++++++++++++++++++++++++++++++++++++
packages/ui/src/Button.tsx | 8 ++++----
apps/web/src/old-component.tsx | 23 -----------------------
4 files changed, 58 insertions(+), 26 deletions(-)
Committed: feat: add task filtering functionality
[main abc1234] feat: add task filtering functionality
4 files changed, 58 insertions(+), 26 deletions(-)
When showing git status, these symbols indicate:
M = ModifiedA = Added (new file)D = DeletedR = RenamedC = Copied?? = UntrackedInteract with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.
Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.
Implement a single phase of a spec. Use when given a spec file and a phase number to implement.
Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.
Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.
Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.