Skip to content
cccskills
FreePublished on GitHub

commit-dis

Save changes made during the current conversation as one Git commit on the current branch. Select specific files, leave unrelated work unstaged, and stop after committing without creating a branch, pushing, or opening a pull request.

OriginalShow the original description

Stage and commit ONLY the work done in this session, on the CURRENT branch — no new branch, no PR, no push. Load whenever the user says 'commit this', 'commit-dis', 'git add commit what we did', 'commit dis', 'save my work', or otherwise asks to commit the changes from the current thread. Enforces: stay on the already-checked-out branch, never overcommit unrelated files.

See how to install

Good for

  • Committing changes made during the current conversation
  • Saving work while excluding unrelated local changes
  • Creating a local commit on the current branch

Files included (1)

  • SKILL.md2.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

commit-dis — commit this session's work, here, now

Stage and commit the changes produced during this conversation onto the current branch. Nothing more. This is the quick "save what we just did" button.

THE RULES

  1. Stay on the current branch. Do NOT create, switch, or rename a branch. Commit wherever HEAD already points — even if that's main. Never run git checkout -b, git switch -c, or git branch.
  2. Only commit what this session changed. Stage the specific files you created or edited in this thread by path. Do NOT git add -A / git add . blindly — that risks sweeping in unrelated working-tree changes, untracked scratch files, or another task's edits. No overcommitting.
  3. No push, no PR. Stop after the commit unless the user explicitly asks to push or open a PR.
  4. One commit for the session's work unless the user asks otherwise.

Steps

  1. Confirm the branch and see what's changed:
    git rev-parse --abbrev-ref HEAD
    git status --short
    
  2. Identify the exact files this session touched. If anything in git status was NOT changed by this session, leave it unstaged. If it's ambiguous whether a dirty file belongs to this session, ask the user rather than guessing.
  3. Stage by explicit path (never -A/.):
    git add <file1> <file2> ...
    
  4. Commit with a clear message describing what this session did. End the message with the standard trailer:
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    
  5. Confirm:
    git log --oneline -1
    

Don't

  • Don't create or switch branches.
  • Don't git add -A, git add ., or git commit -a.
  • Don't push or open a PR.
  • Don't amend or rebase prior commits.
  • Don't stage files you didn't touch this session (build artifacts, other in-flight work, untracked scratch).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

access-policy

FreeSummary

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna20.3KUpdated Oct 19, 2026

account-research

FreeSummary

Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna20.3KUpdated Oct 19, 2026

Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna20.3KUpdated Oct 19, 2026

agent-browser

FreeSummary

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna20.3KUpdated Oct 19, 2026

ap-invoice-match

FreeSummary

Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna20.3KUpdated Oct 19, 2026

billing

FreeSummary

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna20.3KUpdated Oct 19, 2026

See all skills by kortix-ai

Report a problem with this skill