Saad Bash

Bug-fixing workflow that starts by writing a failing test to reproduce the bug, then uses subagents to propose fixes and verifies with passing tests. Use when a user reports a bug, asks to fix a bug, or wants a regression test first.

Behavioral guidelines to reduce common LLM coding mistakes. Use this skill when the user explicitly asks to apply coding rules, coding principles, or disciplined coding guidelines before implementing a task. Trigger on phrases like "/code-rules", "use code rules", "apply coding principles", "follow coding guidelines", or "use disciplined coding".

Rewrites articles, blog posts, essays, bios, and other prose to remove signs of AI-generated writing. Use this skill whenever the user asks to "humanize", "de-AI", "edit for AI tells", "make this sound less AI", or "remove AI writing patterns" from any piece of text. Also trigger when the user pastes text and asks why it sounds robotic, generic, or off, or when they say things like "this sounds like ChatGPT wrote it". The skill diagnoses specific AI writing patterns, explains each one found, and rewrites the text with those patterns removed while preserving the original meaning, voice, and facts.

Remove duplicated code and tech debt by keeping code DRY. Use when asked to de-duplicate logic, extract shared utilities, or refactor repeated patterns ("keep code DRY", "remove duplicated code", "extract common functions", "reduce tech debt"). Include checks for uncommitted changes before refactors.

Address GitHub Pull Request feedback with the gh CLI. Use when a user provides a PR number and asks to fetch comments, verify which comments are meaningful, add regression tests, implement fixes, run all tests, and push the branch.

Create a GitHub Pull Request using the gh CLI after git-incremental-commits has produced a clean working tree. Use when asked to open a PR, create a PR after committing, or "make a PR". Generates a PR body with Summary, Major changes, optional Screenshots, optional Tests, and optional Additional info.

Organize uncommitted changes into atomic Git commits using Conventional Commits. Use before opening a PR or merging to produce a clean, reviewable history where each commit represents one logical change.

Create or update project README.md files by scanning the repository and keeping documentation in sync with the current setup. Use when a README is missing, outdated, or needs updates based on package configs, build/test scripts, env examples, licenses, or changelog files. Include install/usage/env vars/testing/contributing/license/changelog sections only when the repo contains evidence for them.