All authors
Claude Skills by vstlmkh
github.com/vstlmkh8 skills0 installs7 views
- Agile ArtifactsReading a ticket and editing one you already hold — the frontmatter grammar, which fields are yours to change, the legal status transitions, the one-working-tree rule, and the generated boards you must never edit. Load before touching any file under the tracker. Creating a ticket or claiming one out of `todo` is `agile-claims`, which only `pm` and `qa` need.Votes: 0GitHub stars: 3
- Agile DodThe Definition of Done — what "verified" means, the honesty rule and the five waivers, the checklist a ticket must satisfy at review, and how to reject. The six gate contracts themselves are data, printed by `agile.py gates`; this skill is the reasoning around them. Load before declaring yourself ready for review, and before verifying.Votes: 0GitHub stars: 3
- Project KnowledgeHow the agents use the project knowledge base — consulting it before work starts, filing what a task revealed, actualising notes at close, and keeping the graph linked. Load before grooming a ticket, before changing business logic, integrations, domain workflows or architecture, and before closing anything. The convention itself is docs/knowledge/README.md.Votes: 0GitHub stars: 3
- Agile ClaimsCreating tracker artifacts and taking hold of one — ID allocation, the full frontmatter block, the compare-and-swap claim protocol that keeps parallel agents from stealing each other's work, and who may write which part of a spec. Load this only if you create tickets or claim them: `pm` and `qa` do, an engineer never does. Editing a ticket you already hold is `agile-artifacts`.Votes: 0GitHub stars: 3
- Agile LessonsHow the agents record and obey what this project has taught them about working here — reading the rules at the start of a gate, filing one when a ticket bounces, confirming an existing rule instead of duplicating it, and judging a NO-LESSON waiver at gate 5. Load before closing a ticket that was rejected at any gate, and whenever `lessons:` or `lessons_waiver:` has to be set. The convention itself is docs/lessons/README.md.Votes: 0GitHub stars: 3
- designing-databasesDesign, audit and tune relational databases on PostgreSQL and MySQL/InnoDB — table and key design, index strategy, slow-query and EXPLAIN-plan diagnosis, transaction isolation and locking, and zero-downtime migrations in any framework (Alembic, Django, Laravel, Doctrine, Prisma, TypeORM, Knex, Drizzle, Flyway, Liquibase, Atlas, golang-migrate). Use when the user wants to model tables, pick primary keys or column types, decide which index to add or drop, find out why a query or endpoint became...Votes: 0GitHub stars: 3
- Agile GitThe git protocol — branch naming, commit style, PR creation, who may push where, and (in a super-repo) the submodule pointer-bump rules that keep the tracker coherent with the code it describes. Load before any git operation.Votes: 0GitHub stars: 2
- Agile GroomingHow the PM turns a raw request into implementable tickets — decomposition into epics, stories and single-scope tasks, writing acceptance criteria an agent can actually satisfy, prioritising, and triaging bugs. Load before creating or refining anything in the tracker.Votes: 0GitHub stars: 2