← all publishers

finos

@finos source repo

26 published skills

  1. Speckit Implement · finos
    Speckit Implement
    0
    installs
  2. Draft Github Issue · finos
    Draft GitHub issues using repository templates in .github/ISSUE_TEMPLATE. Use when users ask to create, draft, or refine an issue, bug report, feature proposal, support question, meeting agenda, office hours notes, schema change proposal, maintainer update, project proposal, or experimental feature feedback.
    0
    installs
  3. Migrate Xtend Generator · finos
    Migrate an Xtend code generator (rune-lang) to the fluent Java CodeRenderer/CodeWriter API. Use when converting a *.xtend generator class to Java, when asked to "migrate a generator", or when reviewing such a migration. Covers the porting steps, Xtend-to-Java translation patterns, output conventions, verification via regression tests, and parity checking against the old generator.
    0
    installs
  4. React UI Components · finos
    Use when creating React UI components in this repo, including package placement, TypeScript props, exports, showcase examples, and tests. Keywords: create ui component, new React UI component, TSX component, add component test, Playwright component test, Vitest test, showcase example.
    0
    installs
  5. Intent · finos
    Manages intent — features, enhancements, bugs and the reasoning behind them — recorded as prose in the knowledge base with a lifecycle. Use when capturing new work, moving work through backlog, refinement or implementation, releasing or cancelling work, or asking what is pending, in flight, or no longer valid.
    0
    installs
  6. Squire · finos bundle
    Use when morphir-scala work needs environment diagnostics or build/network/sandbox unblocking; reference repository management; branch lifecycle refresh after squash-merging a target branch into main; Morphir IR spec/schema sync or export; or task-tracking configuration and beads mode resolution.
    0
    installs
  7. Kb · finos bundle
    Manages the Morphir knowledge base under kb/ — OKF bundles and concept documents. Use when adding content to a bundle, creating a new bundle, checking the knowledge base for conformance or provenance drift, building or querying its SQLite index, managing intent through its lifecycle, recording or reading architectural decisions as Decision Records, or navigating, searching and listing its bundles, concepts and links.
    0
    installs
  8. Skill Creator · finos bundle
    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
    0
    installs
  9. Release Manager · finos
    Assists with Morphir CLI release management for finos/morphir, including pre-release verification, extension verification, version bumps, tagging, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
    0
    installs
  10. Technical Writer · finos bundle
    Assists with writing and maintaining Morphir technical documentation. Use when creating, reviewing, or updating documentation including API docs, user guides, tutorials, and content for the Docusaurus site. Also helps ensure documentation quality through link checking, structure validation, and code review for documentation coverage.
    0
    installs
  11. Build Threat Catalog · finos
    Create a CCC threat catalog (threats.yaml) for a cloud service — import applicable core threats, define service-specific threats mapped to the service's capabilities, and map each to external frameworks (MITRE ATT&CK, MITRE D3FEND, CISA KEV, CWE, OWASP) via standalone Gemara MappingDocuments in the service's mappings/ directory, validating against schemas/threats-schema.json and schemas/mappingdocument-schema.json. Requires the service folder to already contain metadata.yaml and capabilities.yaml. Use when the user asks to "identify threats for `service`", "create a threat catalog for `service`", or "create threats.yaml" for a service.
    0
    installs
  12. Build Control Catalog · finos
    Create a CCC control catalog (controls.yaml) for a cloud service — import applicable core controls, define service-specific controls mapped to identified threats, and include testable assessment requirements that validate against schemas/controls-schema.json. Use when the user asks to "identify controls for `service`", "create a control catalog for `service`", or "create controls.yaml" for a service.
    0
    installs
  13. Build Capability Catalog · finos
    Create a CCC capability catalog (metadata.yaml + capabilities.yaml) for a cloud service, mapping equivalent offerings across AWS, Azure, and GCP and placing them in the correct catalogs / category folder. Use whenever the user asks to "create a capability catalog" / "capability catalog" for a cloud service, or "create a capability catalog for a service similar to <known service>".
    0
    installs
  14. Build Features And Cloud API · finos
    Implement an approved modules/features/<service>/analysis.md: Gherkin features (reusing generic/ where planned), cloud-api Go package and factory wiring, modules/cloud-api-test/terraform fixtures per cloud, integration_calls.csv, modules/cloud-api-test/privateer-config, cfi-testing/privateer-config/finos-integration, and cfi-testing/actions-config. Use after build-service-behavioural-test-analysis when the user approves analysis and wants behavioural tests runnable end-to-end.
    0
    installs
  15. Build Service Behavioural Test Analysis · finos
    Analyse a CCC service control catalog and produce analysis.md plus a minimal cloud-api interface design for behavioural tests. Use when ingesting catalogs/*/*/controls.yaml, creating modules/features folders, or planning @Behavioural Gherkin scenarios before implementation. Downstream implementation uses modules/cloud-api-test (terraform, integration_calls.csv) and cfi-testing/privateer-config/finos-integration.
    0
    installs
  16. Docs · finos
    Update existing project documentation to reflect the current state of the branch
    0
    installs
  17. Lint · finos
    Check and fix code formatting using ESLint and Prettier
    0
    installs
  18. Issue · finos
    Create a GitHub issue markdown file from a bug report, feature request, or discussion context
    0
    installs
  19. Commit · finos
    Create a conventional commit for the current staged/unstaged changes
    0
    installs
  20. Summary · finos
    Generate a concise implementation summary for a PR description
    0
    installs
  21. Implement · finos
    Implement a GitHub issue end-to-end: fetch the issue, plan, code with approval, commit incrementally, and generate a PR summary.
    0
    installs
  22. Address Review · finos
    Address review comments on a GitHub pull request
    0
    installs
  23. Speckit Plan · finos
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    0
    installs
  24. Speckit Analyze · finos
    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
    0
    installs
  25. Speckit Clarify · finos
    Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
    0
    installs
  26. Speckit Specify · finos
    Create or update the feature specification from a natural language feature description.
    0
    installs