epicodic
Community@epicodic
epicodic provides disciplined software engineering skills covering TDD, debugging, code review, planning, and minimal-code 'ponytail' simplification practices.
Agent Skills by epicodic
Showing 20 vetted skills indexed across 1 GitHub repositories.
git-commit
Generates Conventional Commits messages from staged diffs and commits after user approval.
test-driven-development
Enforces red-green-refactor test-first workflow for features, bugfixes, and refactoring.
systematic-debugging
Diagnose bugs through a four-phase root-cause investigation process before proposing fixes.
dispatching-parallel-agents
Dispatch concurrent agents to investigate independent failures across separate problem domains.
ponytail
Enforces minimal, standard-library-first solutions for coding tasks with adjustable intensity levels.
executing-plans
Executes written implementation plans task-by-task with verification checkpoints and coding-convention reviews.
writing-documentation
Writes structured Markdown documentation for software components and developer guides.
ponytail-audit
Audits an entire codebase for over-engineering and produces a ranked list of deletions and simplifications.
ponytail-help
Displays a quick-reference card of ponytail modes, skills, and commands.
brainstorming
Guides collaborative dialogue to turn ideas into approved design specifications.
ponytail-review
Reviews code diffs for over-engineering and lists what to delete.
writing-plans
Generates detailed multi-task implementation plans from specs with TDD steps and exact file paths.
requesting-code-review
Dispatches a code-reviewer subagent to evaluate git diffs against requirements before merging.
using-skills
Enforces discovery and invocation of applicable skills before any AI response or action.
receiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
writing-skills
Create and test agent skills using test-driven development methodology.
ponytail-gain
Displays a one-shot ASCII scoreboard of ponytail's benchmarked code, cost, and speed reductions.
verification-before-completion
Enforces running verification commands before claiming work is complete or passing.
subagent-driven-development
Executes implementation plans by dispatching fresh subagents per task with ordered review gates.
ponytail-debt
Harvests ponytail: code comments into a grouped technical debt ledger report.
Frequently Asked Questions About epicodic
FAQPage SchemaWhat tasks can I accomplish with epicodic's skills?▼
You can commit staged changes with proper messages, practice test-driven development, debug systematically, write and execute implementation plans, request and receive code reviews, write documentation, and run ponytail modes that enforce minimal, standard-library-first code with repo-wide over-engineering audits.
Who are epicodic's skills designed for?▼
Software engineers and developers who want disciplined coding practices: TDD practitioners, reviewers hunting over-engineering, and teams executing multi-step plans with verification checkpoints. The ponytail suite targets anyone fighting bloat, boilerplate, and unnecessary dependencies in a codebase.
How do the ponytail skills work in practice?▼
Invoke ponytail with lite, full, or ultra intensity on any coding task to force the simplest working solution. Use ponytail-review on diffs, ponytail-audit on whole repos, ponytail-debt to harvest deferred-shortcut comments into a ledger, and ponytail-gain or ponytail-help for scoreboards and command references.
What license and cost apply to epicodic's skills?▼
The ponytail skill is explicitly licensed under MIT, permitting free use, modification, and redistribution. Other skills in the manifest do not state a license, so users should check individual repository folders before commercial redistribution.
What prerequisites or dependencies do these skills require?▼
No external dependencies are specified in the manifest. Skills are invoked by trigger phrases or slash commands within a skill-capable session; using-skills establishes discovery at conversation start, and verification-before-completion requires the ability to run project test and build commands.