enocgit
UserA portable, tool-agnostic, plan-gated pipeline for building quality software with AI agents.
Categories
Indexed Skills (15)
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
address-review
Triages review comments on an open pull request — from humans and from bots (CodeRabbit, bugbot, Codex, Sourcery, …) — and addresses them. Reads every comment, verifies and challenges each one against the code, the frozen contract, and the ADRs to weed out false positives, then auto-fixes the trivial and gates the rest behind a plan. Manually invoked, standalone — not tied to a pipeline stage. Use when the user says "address the PR reviews", "go through CodeRabbit's comments", "handle the bugbot findings", "handle the codex findings" or "respond to the review".
feature-start
Starts implementation of one decomposed task: isolates a workspace (a feature branch by default; a git worktree only when isolation is critical), loads the relevant PRD, ADR, and frozen contract, then proposes a compact in-session plan for approval before any code is written. Use at the start of Stage 4 (Implement) once scope is approved, or when the user says "start working on issue #N", "begin this task", or "let's implement {feature}".
sdlc
Orchestrates an end-to-end, plan-gated software build pipeline: routes each stage to the right skill while enforcing human approval gates. Covers discovery, PRD, stress-test, architecture, API contracts, decomposition, implementation, QA, review, landing, and retro. The single entry point for the workflow. Use when the user wants to build a feature or product the disciplined way, start or resume structured development, asks "what stage are we at" / "what's next", or says "start the sdlc" / "run the pipeline".
definition-of-done-review
Reviews a change against this team's Definition of Done before merge. It goes beyond generic code review by checking acceptance criteria, contract fidelity, proportional verification and test coverage, docs/ADR updates, and security for sensitive areas, then gives a pass/fail verdict with evidence appropriate to each item. Use at Stage 6 after code-review and simplify, or when the user asks "is this ready to merge" or "run the DoD check".
project-status
Reports project status from the live tracker (GitHub Issues/Projects). Access is read-only for external trackers. In local-only mode, the skill maintains docs/progress.md as the tracker itself. Use when the user asks "what's the project status", "where are we on {epic}", "what's next", or wants a Now/Next/Blocked view; also to disclose the breakdown after Decompose (Stage 3) or the state after landing a PR (Stage 7).
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
unslop
Apply to human-facing communication and prose to remove AI writing tells while preserving meaning, evidence, and the intended tone.
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.