amitkot

@amitkot source repo

21 skills
0 followers
6 hours ago last updated

▌
Ralph · amitkot
Interactive planning and build loop for Claude Code. Generates specs, implementation plans, and iterative build infrastructure (loop.sh) through clarifying questions. Use when starting a multi-step feature, bugfix, or refactoring task.

0
installs
▌
Deepwiki · amitkot
ALWAYS use when the user mentions an external repository, library, or protocol by name. Queries any public GitHub/GitLab/BitBucket repository to answer questions about its code, APIs, behavior, or implementation without cloning it.

0
installs
▌
Git Fundamentals · amitkot
Essential Git version control knowledge including repositories, commits, branches, remotes, and common workflows. Use when helping with basic Git operations, teaching Git concepts, or as foundation for advanced Git tools. Activate for questions about Git basics, standard workflows, or version control fundamentals.

0
installs
▌
Slack Notify · amitkot
Use when the user asks to send Slack notifications, create task threads, post progress updates, read thread replies, or wants session activity reported to Slack.

0
installs
▌
Gitbutler CLI · amitkot bundle
MANDATORY when on 'gitbutler/workspace' branch. Use `but` commands instead of git for commits, pushes, staging. Key commands: `but status -v`, `but stage <file> <branch>`, `but commit -m 'msg' <branch>`, `but push <branch>`. Invoke this skill BEFORE any git commit/push when gitbutler/workspace is the current branch.

0
installs
▌
Cmux Browser · amitkot
Use this when testing the dashboard with a web client in interactive sessions. Best for testing frontend tools, verifying UI behavior, checking page loads, validating URL routing, or interacting with the browser. Preferred over playwright-testing for interactive work — the browser opens as a visible split pane and results return inline.

0
installs
▌
One Test One Thing · amitkot
Use when writing or reviewing a unit/integration test — enforces a clear scenario-shaped name (no `_and_`), Arrange/Act/Assert structure with visible separation, and one logical behaviour per test. A failing test name should describe exactly what regressed without opening the file. Multiple scenarios become multiple tests, not one test with branches or `_and_` in the name.

0
installs
▌
Deliverable On Disk · amitkot
Use when about to mark a task as complete, done, finished, or shipped — verifies the deliverable actually exists as a file on disk, in a commit, or as a posted artefact. Blocks claiming completion based on chat output alone.

0
installs
▌
Extend Not Duplicate · amitkot
Use when about to write a new script, command, or file that is near-identical to an existing one with small variations — adds a CLI flag, parameter, or config option to the existing script instead of creating a parallel copy.

0
installs
▌
Plans To Beads · amitkot bundle
This skill should be used when the user asks to "convert plan to beads", "create beads from plan", "break down plan into tasks", "create implementation plan", or has a plan file to track with beads. Transforms a plan into a tracked implementation plan with beads, dependency graph, and verification criteria.

0
installs
▌
Playwright Testing · amitkot
ALWAYS use this when testing a website with a web client. This skill should be used when testing frontend tools, verifying UI behavior, checking page loads, validating URL routing, or interacting with the browser in any way.

0
installs
▌
Ephemeral State In Tmp · amitkot
Use when about to write a state, cursor, marker, scratch, or progress file for a cron loop, monitor task, polling job, recurring schedule, or any session-scoped/ephemeral data — directs the file to /tmp/<name>.json instead of ~/.claude/ or other config dirs.

0
installs
▌
Offline Questions · amitkot
Use when the user wants to park a question for later — fires a background subagent that researches with full session context and appends a structured answer to ~/Desktop/Offline_Questions_and_Answers.md. Trigger phrases include "park this question", "research this offline", "I care about this but not now", or invocation via /offline-question.

0
installs
▌
Comment Non Obvious Steps · amitkot
Use when writing or editing code that contains repeated-looking calls on different structures, bitmask/bit-fiddling, ordering-sensitive sequences, or multi-step state mutations across data structures — adds a short inline comment per step explaining WHY each step is distinct, so a reader doesn't stop and ask "wait, why are there three of these?". Does not apply to trivial code with self-explanatory identifiers.

0
installs
▌
Evidence Over Speculation · amitkot
Ground claims in evidence; never present speculation as fact

0
installs
▌
Marketplace Author · amitkot bundle
This skill should be used when the user asks to "create a skill in this repo", "add a skill to claude-code-tools", "add a skill to the marketplace", "update an existing skill", "ship this skill", "bump skill version", or otherwise authors/edits skills in the amitkot/claude-code-tools marketplace. Handles directory layout, version bumps across SKILL.md / plugin.json / marketplace.json, CHANGELOG entries, and the create → commit → push → PR → /plugin → /reload-plugins workflow.

0
installs
▌
Execute Beads Plan · amitkot bundle
This skill should be used when the user asks to "execute implementation plan", "run beads plan", "start working on plan", "execute tasks from plan", or wants to run an implementation plan that was created with plans-to-beads. Orchestrates parallel task agents with verification and change handling.

0
installs
▌
Conversation Search · amitkot bundle
Find and resume Claude Code conversations by searching topics or filtering by date. Returns session IDs and project paths for easy resumption via 'claude --resume'. Use when user asks "find that conversation about X", "what did we discuss", "what did we work on yesterday", "summarize today's work", "show this week's conversations", "recent projects we accomplished", or wants to locate past work by topic, date, or time period (yesterday, today, last week, specific dates).

0
installs
▌
Pr Update Description · amitkot
Update a PR with a clear explanation of the changes. Use when the user asks to update, write, or improve a PR description, or mentions "pr description", "update PR", or "describe PR".

0
installs
▌
Plans And Investigations Location · amitkot
Use when about to write an implementation plan, investigation note, design sketch, post-mortem, or any markdown capturing personal process inside a project repo — and especially when about to save under `docs/plans/`, `docs/investigations/`, or `docs/design/`. Routes personal/in-flight work to `.local/<kind>/` (gitignored) and reserves `docs/<kind>/` for shared, team-reviewed artefacts.

0
installs
▌
Conversation Search Setup · amitkot
Use when the user asks to "set up conversation search", "install conversation search", "install cc-conversation-search", "/conversation-search:setup", or when the `conversation-search` run skill reports that the CLI is missing. Idempotently installs (or upgrades) the upstream `cc-conversation-search` PyPI tool via `uv tool` and initialises the local SQLite FTS5 index at `~/.conversation-search/index.db`. Safe to re-run.

0
installs

21 published skills