Use when: multiple independent coding, debugging, or research tasks can be investigated in parallel.
Skills in this repository
kimtth/agent-skill-100-lines-or-less - Page 3
SkillsMP has collected 99 skills from kimtth/agent-skill-100-lines-or-less. Open a skill to review its source and details.
kimtth/agent-skill-100-lines-or-lessShowing 19 of 99 collected skills.
Use when: execute a written implementation plan with checkpoints, verification, and blocker handling.
Use when: find, compare, install, update, or remove agent skills from skills.sh or a source repo.
Use when: implementation is complete and you need to verify, summarize, and choose merge, PR, commit, or cleanup flow.
Use when: create a conventional git commit from the current diff with logical staging and message analysis.
Use when: create or review optimized multi-stage Dockerfiles for smaller, safer, reproducible application images.
Use when: generate a Playwright test from a user scenario by first exploring the UI and then saving a passing test.
Use when: improve PostgreSQL schema, queries, indexes, JSONB, arrays, full-text search, or performance with Postgres-specific features.
Use when: handling code review feedback before implementing suggestions or pushing back.
Use when: improve code structure, readability, type safety, or maintainability without changing external behavior.
Use when: discover, install, list, check, update, remove, back up, restore, sync, or initialize Agent Skills with bunx/npx skills.
Use when: break a plan, spec, or PRD into independently grabbable implementation issues.
Use when: turn current conversation and repo context into a PRD for an issue tracker.
Use when: starting feature work that should be isolated from the current checkout or branch.
Use when: about to claim work is complete, fixed, passing, or ready for commit or PR.
"Use when: review UI code, audit accessibility, check UX, or compare a site against current Web Interface Guidelines."
Use when: create or improve an agent skill with proper frontmatter, structure, triggers, and progressive disclosure.
Use when: step back from unfamiliar code and map surrounding modules, callers, concepts, and ownership before editing.
Clean up dead code, obsolete paths, and contradictions in the codebase to keep it small, correct, and aligned with reality.