pratiyush
- 41 skills
- 0 followers
- 6 hours ago last updated
- ▌ SQL Migration · pratiyush bundleTurn a Jira ticket into a draft GitLab MR containing a paired forward + rollback SQL migration that follows this repo's conventions. Trigger on phrases like "work <JIRA-KEY>", "create migration for ticket", "draft SQL for <KEY>".
- ▌ Reverse Engineer · pratiyushOne-off, operator-run skill that reverse-engineers house coding standards, conventions, and anti-patterns from a repository's git history and GitLab MR discussions, then proposes concrete edits to the sql-migration skill's artifacts. Trigger phrases like "reverse engineer conventions", "mine review comments", "audit the sql-migration flow".
- ▌ SQL Conventions Miner · pratiyushOne-time skill to mine the SQL migrations repo's git history and produce draft conventions.md, templates/, examples/, and anti-patterns.md for the sql-migration runtime skill. Trigger phrases like "mine SQL history", "refresh conventions", "bootstrap sql-migration artifacts".
- ▌ Wiki All · pratiyushRun the complete llmwiki pipeline from scratch — init, sync, graph, build, lint, and serve. Use when the user says "run everything", "full pipeline", "wiki-all", or wants to rebuild the entire wiki from session history.
- ▌ Self Learn · pratiyushExtract reusable patterns from recent sessions, propose framework improvements, and (with approval) update the framework docs. This is the dogfooding meta-loop — the project learns from its own usage. Use when the user says "learn from this", "what did we learn", "extract lessons", "update the framework", "add this to steering rules", or after completing any substantial feature or debugging session.
- ▌ Llmwiki Sync · pratiyushSync Claude Code session transcripts into the user's llmwiki and ingest them into the wiki. Use when the user says "sync the wiki", "update llmwiki", "ingest recent sessions", "refresh the knowledge base", or asks a knowledge question that would benefit from up-to-date sessions. Also use when the user explicitly asks to refresh or rebuild the LLM wiki from their agent history.
- ▌ Llmwiki Query · pratiyushAnswer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki first before falling back to external search.
- ▌ Llmwiki Ingest · pratiyushIngest one source document (or a folder of them) into the llmwiki. Use when the user drops a new markdown file, PDF, or URL into the wiki and asks you to process it. The user will typically say "ingest this", "add this to the wiki", "process this file into the wiki", or point at a file under `raw/`.
- ▌ Project Maintainer · pratiyushMaintain an llmwiki-style open-source project across the full framework pipeline. Use when the user says "maintain the project", "check my tasks", "update progress", "run phase gate", "do a monthly verify", "lint my wiki", "check stale entries", or invokes any form of ongoing project-keeping chore. Reads _progress.md, tasks.md, docs/roadmap.md, and .github issues to figure out what's next and what's drifted.
- ▌ Hello Skill · pratiyush bundleGenerate friendly greeting messages in multiple languages. Use when the user asks for a hello message, welcome text, or localized greeting.
- ▌ Code Quality · pratiyush bundleAnalyze Java source files for code quality issues including style violations, complexity warnings, and common anti-patterns. Use when reviewing Java code, running quality checks, or preparing for code review.
- ▌ Release Notes · pratiyush bundleMaintain project release notes, changelogs, and framework phase updates. Use when the user asks to generate a changelog, draft release notes, update CHANGELOG.md, or track framework phase transitions.
- ▌ Skill Template · pratiyush bundleScaffold new Agent Skills with best-practice structure and frontmatter. Use when the user wants to create a new skill, bootstrap a skill directory, or generate SKILL.md boilerplate following the Agent Skills spec.
- ▌ Test Generator · pratiyush bundleGenerate test file stubs and boilerplate from source code analysis. Use when the user asks to create tests, add test coverage, or scaffold test files for existing source code.
- ▌ Data Validation · pratiyush bundleValidate CSV and JSON data files against schemas and quality rules. Use when the user asks to check data quality, validate a dataset, or verify file contents match an expected schema.
- ▌ Dependency Audit · pratiyush bundleAudit project dependencies for known vulnerabilities, outdated packages, and license compliance issues. Use when the user asks to check dependencies, audit packages, review licenses, or assess supply chain security.
- ▌ Project Maintenance · pratiyush bundleMaintain project health by enforcing PR checklists, tracking open issues, verifying release readiness, and ensuring framework phases are up to date. Use when reviewing PRs, creating issues, preparing releases, or auditing project state.
- ▌ Basic Skill · pratiyushA minimal example skill that demonstrates the Agent Skills format. Use when learning how to create skills.
- ▌ Skill With Tests · pratiyush bundleExample skill demonstrating the test scenario format from the extended specification. Use when learning how to write and evaluate skill test cases.
- ▌ Skill With Scripts · pratiyush bundleExample skill that bundles executable scripts for automated tasks. Use when you need to run shell-based automation via bundled scripts.
- ▌ Skill With Extended · pratiyushDemonstrates extended spec features. Use when learning about security, testing, composition.
- ▌
- ▌
- ▌ Extended Skill · pratiyushFixture for extended spec validation tests. Use when testing extended fields.
- ▌ Skill With Ignore · pratiyush bundleA test skill with a .skillignore file. Use when testing filterFiles behavior.
- ▌ Dev Spec Kit Graph · pratiyushBuild, refresh, and read dev-spec-kit's Verified Traceability Graph — provider-agnostic. Keep it fresh with the build wrapper, read blast radius / implements-edges / drift to answer "what breaks if this changes?", and run the staleness re-prove dance. For choosing and configuring the code-graph engine itself, see the dev-spec-kit-revitify and dev-spec-kit-graphify skills.
- ▌ Dev Spec Kit Judge · pratiyushSupply an LLM acceptance verdict for a dev-spec-kit `judge` check — for criteria a test can't assert (tone, copy quality, "is this error actionable", a transcript vs a rubric). Use when a @check kind=judge needs proving in harness mode (no API key needed — you are the LLM).
- ▌ Dev Spec Kit Retro · pratiyushRun the dev-spec-kit learning loop — capture lessons after a feature/incident into .dev-spec-kit/learnings.md, propose promotions into the laws, and turn fixed bugs into permanent regression checks. Use after completing a feature, after any surprising failure, or when the user says retro.
- ▌ Dev Spec Kit Finish · pratiyushThe completion ritual — run when a feature's tasks are done and it's time to land the branch. Fresh-evidence entry gate, a fixed option menu, typed confirmation for destructive paths, provenance-checked cleanup, every step journaled. Use when the user says finish/land/merge/wrap up, or after dev-spec-kit pr is ready.
- ▌ Dev Spec Kit Intake · pratiyushTurn a raw idea, voice-dump, or ticket into a dev-spec-kit intake file and route it. Use when the user brain-dumps a request, pastes a Jira/GitHub/GitLab ticket, or points at an idea that has no spec yet.
- ▌ Dev Spec Kit Review · pratiyushTwo-pass adversarial code review for dev-spec-kit changes — a blind diff-only pass, then a full-context pass against the spec and graph. Use before any PR, after dev-spec-kit graph build is green, or when the user asks for review.
- ▌ Dev Spec Kit Analyze · pratiyushScore each requirement's complexity 1–10 and recommend a subtask breakdown, then expand the over-scoped ones into bound sub-criteria. Use after a spec is drafted and before implementation, to catch requirements that are too big to prove as a single unit.
- ▌ Dev Spec Kit Clarify · pratiyushResolve ambiguity in a raw intake or draft spec by asking the user ≤5 high-value questions, each with a recommended default. Use before finalizing a full-spec route, or when `spec.onVague` is "clarify", or whenever a requirement is under-specified.
- ▌
- ▌ Dev Spec Kit Research · pratiyushAugment a requirement or intake with current, cited best-practice before it's finalized — search the web, read the sources, and write findings back as linked evidence. Use when a spec touches a fast-moving area (a protocol, a library API, a security pattern) the model shouldn't answer from memory.
- ▌ Dev Spec Kit Revitify · pratiyushdev-spec-kit's default code-graph provider — the bundled revitify engine (native TypeScript, tree-sitter multi-language). Zero install, zero API key, always available. Use to understand when revitify is the right provider, how it is configured, what it can and cannot index, and how it feeds the Verified Traceability Graph. For the build/read loop itself, see dev-spec-kit-graph.
- ▌ Dev Spec Kit Workflow · pratiyushDrive spec-driven development with dev-spec-kit — route the request, write EARS specs with @check bindings, derive evidence-bound tasks, TDD, prove checks with real test runs, build the Verified Traceability Graph, record approvals, and generate graph-derived PR bodies. Use whenever the user asks to build/change code in a dev-spec-kit-initialized project (.dev-spec-kit/ present) or mentions rivet, specs, EARS, or traceability.
- ▌ Dev Spec Kit Architect · pratiyushTurn approved requirements into a thin high-level design and the Architecture Decision Records (ADRs) that justify the non-obvious choices. Use after requirements are clarified and before implementation, or when a change makes a load-bearing architectural decision.
- ▌ Dev Spec Kit Spec Author · pratiyushWrite high-quality dev-spec-kit specs — Gherkin scenarios (default) or EARS acceptance criteria with @check bindings in .dev-spec-kit/specs/*.md. Use when authoring or revising a spec, converting a ticket/idea into requirements, or when criteria are vague, untestable, or unbound.
- ▌ Dev Spec Kit Test Author · pratiyushDraft descriptive, behavior-asserting tests from acceptance criteria — run `dev-spec-kit spec draft-tests` to scaffold failing stubs, then flesh each with real assertions covering the 4 edge categories. Use in the TDD red phase, or whenever a criterion is unbound or its test is shallow.
- ▌ Revitify · pratiyushQuery this project's code knowledge graph (built by revitify — graphify's output contract, native TypeScript). Use when the user asks how code hangs together, what breaks if something changes, where a concept lives, or wants the graph rebuilt/visualized.