All authors
Claude Skills by TheMostlyGreat
github.com/TheMostlyGreat15 skills0 installs2 views
- AuditRun comprehensive code audit for architecture, dead code, and testVotes: 0GitHub stars: 19
- BddBehavior-first feature development — use when building newVotes: 0GitHub stars: 19
- BrainstormUse when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.Votes: 0GitHub stars: 19
- Cleanup ZombiesKill zombie dev servers and test processes. Use when ports areVotes: 0GitHub stars: 19
- DebugRoot cause debugging before fixes. Use when investigating bugs,Votes: 0GitHub stars: 19
- ElicitExtract tacit knowledge through non-obvious microquestions — things only the user knows that can't be found in code, docs, or research. Use when you're about to guess at intent, context, or constraints during SAFEWORD's understanding flow. Also use when user says 'ask me', 'what do you need to know', or when another skill (bdd, brainstorm, debug) needs user context before proceeding. Do NOT use for questions answerable by reading the codebase or searching the web.Votes: 0GitHub stars: 19
- Figure It OutExplore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstor...Votes: 0GitHub stars: 19
- LintRun linters and formatters to fix code style issues. Use whenVotes: 0GitHub stars: 19
- Quality ReviewDeep code review with web research. Use when double-checking codeVotes: 0GitHub stars: 19
- RefactorImprove code structure without changing behavior. Use whenVotes: 0GitHub stars: 19
- Self ReviewUse when finishing spec.md before writing test-definitions.md, orVotes: 0GitHub stars: 19
- Tdd ReviewUse when completing a TDD step and wanting a quality check. Reviews test quality after RED, implementation correctness after GREEN, and scenario completeness after REFACTOR.Votes: 0GitHub stars: 19
- TestingHow to write good tests. Use when writing tests, improving testVotes: 0GitHub stars: 19
- Ticket System**Purpose:** Context anchor to prevent LLM loops during complex work. Colocates all artifacts. **Creating a ticket:** Run `safeword ticket new <slug>` (optionally with `--type=patch|task|feature` and `--title="..."`). The CLI mints a 6-char Crockford Base32 ID, creates the folder atomically, and writes a starter ticket.md. **Do not scan the tickets directory and pick the next ID yourself** — that races between parallel sessions and silently collides across git branches. **Location:** `.safewo...Votes: 0GitHub stars: 19
- VerifyVerify ticket completion criteria — use when finishing a ticket,Votes: 0GitHub stars: 19