Claude Skills by sillsdev

github.com/sillsdev

44 skillsA× 442 installs72 views

Atlassian Readonly SkillsARead-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects. Use when users need to look up or query a Jira issue -- including any LT-prefixed FieldWorks ticket. Excludes every write operation, so it cannot modify anything.businesspythonshellVotes: 0GitHub stars: 111
Atlassian SkillsAPython utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects. Use when users need to create, update, comment on, link or transition a Jira issue, or search Jira with JQL -- including any LT-prefixed FieldWorks ticket.businesspythongoVotes: 0GitHub stars: 111
Execute ImplementAImplement the approved plan or design with minimal scope and adherence to repo conventions.datagitVotes: 0GitHub stars: 111
Fieldworks WinappAControl and document the FieldWorks desktop application with WinForms MCP or WinApp MCP. Use this skill whenever a task requires launching FieldWorks, restoring or opening a FieldWorks project, walking WinForms UI flows, collecting manual screenshots, reproducing UI bugs, or verifying a fix inside the live FLEx application.datagonodeVotes: 0GitHub stars: 111
Grill With DocsAGrill the user against a repo-local CONTEXT.md, sharpen ambiguous terminology, ground terms in code, and update shared language before implementation. Use when shaping a feature, bugfix, refactor, or repo workflow in an existing codebase.datagitapiVotes: 0GitHub stars: 111
Jira BugfixAEnd-to-end JIRA bugfix workflow: fetch issue, assign, branch, TDD, fix, test, update AGENTS.md, commit, PR, and update JIRA. Use when the user says "fix LT-XXXXX" or references a JIRA bug to resolve.code-qualityrustgoVotes: 0GitHub stars: 111
Openspec Archive ChangeAArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.databashrailsVotes: 0GitHub stars: 111
Openspec Bulk Archive ChangeAArchive multiple completed changes at once. Use when archiving several parallel changes.databashrailsVotes: 0GitHub stars: 111
Openspec Continue ChangeAContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.databashrailsVotes: 0GitHub stars: 111
Openspec ExploreAEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.datagobashVotes: 0GitHub stars: 111
Openspec Ff ChangeAFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.datagobashVotes: 0GitHub stars: 111
Openspec New ChangeAStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.databashrailsVotes: 0GitHub stars: 111
Openspec OnboardAGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.datatypescriptgoVotes: 0GitHub stars: 111
Openspec Propose ChangeACreate a change and generate all artifacts needed for implementation in one go. Use when the user wants the preferred OpenSpec fast path for a new proposal.datagobashVotes: 0GitHub stars: 111
Openspec Sync SpecsASync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.datagorailsVotes: 0GitHub stars: 111
Openspec Verify ChangeAVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.databashVotes: 0GitHub stars: 111
Plan DesignAPlan and design a change set. Define scope, constraints, risks, and acceptance signals before implementation.datagoVotes: 0GitHub stars: 111
PowershellAPowerShell best practices for scripts used in FieldWorks (dev scripts & CI helpers). Use when writing or modifying PowerShell scripts in scripts/ or Build/Agent/.datagoshellVotes: 0GitHub stars: 111
Pr PreflightAThe required entrypoint whenever asked to write, make, open, create, update, or ship a PR for this repo -- do not post a PR body without running this first. Also use for pre-PR review, branch readiness, author interview, review summary generation, or validation evidence.code-qualitygoc++Votes: 0GitHub stars: 111
Respond To Review CommentsARespond to Copilot and human PR reviewer comments: evaluate feedback, fix sensible requests, ask about ambiguity, verify, commit, push, reply to threads, resolve addressed comments, and summarize results. Use when handling review comments, Copilot review feedback, requested changes, unresolved PR threads, or reviewer follow-up.code-qualitygoc#Votes: 0GitHub stars: 111
ReviewAReview changes for correctness, style, and risk; propose fixes or follow-ups.datasecurityVotes: 0GitHub stars: 111
Rubric VerifyAVerify changes with a weighted, repository-grounded rubric and explicit hard gates.datagogitVotes: 0GitHub stars: 111
Sil Library ReuseAReuse lower-level SIL libraries before writing custom helpers in FieldWorks. Use this whenever a task touches file or directory I/O, locked-file retries, paths or URIs, writing systems, keyboards, LCM caches/project IDs/service locators, linked files/media/config paths, localization, LIFT/import/export, FLExBridge or Chorus sync/merge flows, analytics/telemetry, morphology or NLP, scripture/Paratext integration, or SIL test helpers. Even for small fixes, check the package families and repo pa...datagoc#Votes: 0GitHub stars: 111
Smart Screenshot CaptureACapture high-quality screenshots with MCP tools. Use when the user asks to take a screenshot, show the screen, capture a window, document UI evidence, collect before/after images, inspect browser output, or verify a desktop app visually with WinForms MCP, WinApp MCP, browser screenshots, image previews, annotations, or screenshot diffs.datashellVotes: 0GitHub stars: 111
Verify TestAVerify behavior and run appropriate tests to confirm the change set.testingVotes: 0GitHub stars: 111
Commit MessagesAMUST use before writing any git commit message in this repository. Covers the gitlint rules CI enforces (title/body length, blank line, trailing punctuation) and how to write a compliant message on the first try.datagoshellVotes: 0GitHub stars: 111
Convert DialogADrive the conversion of one WinForms dialog to Avalonia through analysis, developer alignment, integration-test planning, exemplar mapping, design, and scaffold/implement. Use when the user invokes /convert-dialog with a dialog class name, or asks to start converting a specific WinForms dialog.designgoexpressVotes: 0GitHub stars: 111
Convert SliceADrive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement. Use when the user invokes /convert-slice with a slice class or layout identity, or asks to convert a slice type or an Unsupported detail row.designgonodeVotes: 0GitHub stars: 111
Create Integration TestATurn a [class]-integration-test-plan.md into headless integration tests, one per plan item, each driving the scenario, asserting the outcome, and capturing a labeled snapshot. Use for TDD before implementation or as verification after it, whenever a test plan exists under Docs/migration/working/.testingtestingVotes: 0GitHub stars: 111
Dependabot ConsolidationACombine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy .github/commit-guidelines.md, verify locally, push, open the combined PR, wait for CI, and close the superseded PRs once it is green. Use when asked to combine, consolidate, batch, roll up, or squash together existing Dependabot PRs.documentationgoshellVotes: 0GitHub stars: 111
Dialog UpdateAKeep a FieldWorks dialog's WinForms (old) and Avalonia (new) implementations in sync whenever either is changed. Use whenever you add, edit, or review a control, field, button, validation rule, apply-order step, or string in a dialog that exists in BOTH a WinForms form (e.g. LexOptionsDlg) and its Avalonia replacement (e.g. LexOptionsDlgView + AvaloniaOptionsDialogLauncher) — even for a one-line change. Also use before claiming a migrated dialog is at parity, and when deciding whether a diffe...datagoVotes: 0GitHub stars: 111
Fieldworks Avalonia UiABuild, review, or fix Avalonia UI code in FieldWorks: XAML, MVVM, view models, owned controls, headless tests, preview host, accessibility identity, and product-vs-preview wiring. Use for any change under Src/Common/FwAvalonia/, Src/Common/FwAvaloniaPreviewHost/, or Src/**/*.Avalonia/, and for net48/net8 Avalonia test changes — even if the request only mentions a control, a binding, a style, or a flaky UI test. For whole-surface migration planning use fieldworks-winforms-to-avalonia-migration...designgoc#Votes: 0GitHub stars: 111
Fieldworks Code CommentingAThe FieldWorks code-comment standard for C#, C/C++, IDL, PowerShell, and project-file/Avalonia-view XML comments. Use whenever writing or editing a comment anywhere in this repository -- new code, refactors, or comment audits, in .cs, .cpp/.h, .idl, .ps1, .csproj/.vcxproj/.props/.targets, or .axaml alike. Covers doc-comment contracts, banned content categories, the 200-character cap on implementation comments, legacy references, XML doc tags, and XML-doc placement.datagoc++Votes: 0GitHub stars: 111
Fieldworks Localization ReviewAReview or change FieldWorks user-facing strings: LocalizationManager/XLIFF and legacy .resx resources, localization keys, the StringTable strategy for XML-configuration labels, Crowdin-facing assets, and localization-sensitive automation metadata. Use whenever a change adds or edits any user-visible text in WinForms or Avalonia, adds a new UI project, touches resource files, or claims localization parity — even for a single new label or error message.datac#nodeVotes: 0GitHub stars: 111
Fieldworks Managed Netfx ReviewAReview or change FieldWorks managed C# code that crosses the .NET Framework 4.8 / C# 7.3 vs SDK-style net8 boundary: project files, language-feature compatibility, test discovery across both runtimes, UI-thread marshaling, and deterministic disposal. Use whenever a change touches a .csproj, adds C# to an unfamiliar project, moves code between net48 and net8 projects, or changes test runners — even if the compile passes locally.datagoc#Votes: 0GitHub stars: 111
Fieldworks Migration Scope ReviewAReview the scope and evidence claims of large FieldWorks migration PRs, OpenSpec changes, and foundational branches. Use when sizing or splitting a branch, judging draft-PR readiness, verifying that checked tasks match their evidence, or whenever a reviewer or author asks whether a migration PR is too big, mixed, or trustworthy.datarustVotes: 0GitHub stars: 111
Fieldworks Semantic Render ParityACapture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR. Use whenever a task creates or evaluates snapshot tests, screenshot baselines, view-definition compilation output, or any claim that an Avalonia view matches its WinForms predecessor.designnodeperformanceVotes: 0GitHub stars: 111
Fieldworks Test CoverageACheck that new or changed FieldWorks code is actually exercised by tests, using test.ps1 -Coverage. Use whenever writing tests for a change, before claiming a bug fix or feature is covered, or when reviewing whether "tests pass" also means the new logic runs under test.datac++Votes: 0GitHub stars: 111
Fieldworks Ui Wiring ReviewAReview or change FieldWorks UI wiring — app-setting and PropertyTable routing, mediator notifications, current-content switching, host replacement, preview-vs-product boundaries, and the global legacy-vs-Avalonia UI selection. Use whenever a change touches which UI host is active, how a setting reaches a screen, RecordEditView/currentContentControl routing, save/PrepareToGoAway paths, or fallback behavior — even if the diff looks like a one-line settings change.datagoVotes: 0GitHub stars: 111
Fieldworks Uia2 Parity TestingADesign or review FieldWorks UI automation and accessibility tests: UIA2, FlaUI, Appium, WinAppDriver, Avalonia.Headless, keyboard, focus, IME, and automation-id strategy. Use whenever a task adds, changes, or evaluates automated UI tests or accessibility/workflow parity claims for WinForms or Avalonia views — including deciding whether a test belongs in the headless or desktop environment.designgoshellVotes: 0GitHub stars: 111
Fieldworks Winforms To Avalonia MigrationAEnd-to-end playbook for migrating any FieldWorks WinForms UI (DataTree slices, XMLViews browse/table, dialogs, choosers, launchers, shell panes) to Avalonia using the established detail/seam architecture. Use whenever planning, implementing, or reviewing WinForms-to-Avalonia work — including seam extraction, region composition, owned controls, plugin editors, parity evidence, or retiring legacy UI — even if the request only says port, modernize, replace WinForms, or new Avalonia view. Also us...testinggoshellVotes: 0GitHub stars: 111
Openspec Apply ChangeAImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.datagobashVotes: 0GitHub stars: 111
Pr PitchANOT an entrypoint -- pr-preflight calls this for the write-up step; use pr-preflight for a fresh 'write/make/open a PR' request. Invoke this directly only to redo the write-up on a PR that already exists. Composes a PR body as a pitch that answers the unknowns a reviewer arrives with, with the branch's decisions, provenance, and paths-not-taken folded into collapsed accordions below it, while evicting those files from the repo.datarustgoVotes: 0GitHub stars: 111
Jira IssueAWrite and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line. Use whenever asked to file, raise, report or create a Jira issue or LT ticket, to turn a user report or a finding into a ticket, or to restructure a ticket that buries its point. Interviews, hunts duplicates before drafting, gets a three-line lede approved, and moves the analysis to a comment.datagogitVotes: 0GitHub stars: 111