Mark Murphy avatar

Mark Murphy

Community

@commonsguy

6,518Followers
|
35Public Repos
|
1Published Skills

Author of several books on Android app development (https://commonsware.com). Maintainer of several open source Kotlin Multiplatform projects, mirrored here.

Skills Distribution
DomainDeveloper To...Kotlin Multiplatform (40%)Android Test Cover.. (35%)Release Quality Ga.. (25%)

Agent Skills by Mark Murphy

Showing 1 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Mark Murphy

FAQPage Schema
What tasks can I automate using Mark Murphy's kover-gate-report?

It runs the KoverGate coverage gate after tests are written or changed, reports where Kotlin or Android coverage fell below the gate, and guides fixes by pointing to gaps that need more tests. It is focused on coverage enforcement, not general refactoring or feature delivery.

Who is the intended user for kover-gate-report?

Android and Kotlin Multiplatform engineers maintaining CommonsWare-style projects, especially contributors who edit tests and need immediate feedback on coverage regressions. It also fits maintainers enforcing quality bars before merge, release, or publication of shared Kotlin libraries.

How do I run kover-gate-report in practice?

Place the kover-gate-report skill in the project environment, open a Kotlin Multiplatform or Android codebase with Kover coverage, modify tests, then run the gate. Review failed checks, add targeted tests, and rerun until the reported coverage gate passes.

Is kover-gate-report open source or paid?

The provided manifest does not state a license or price, so cost cannot be confirmed from the supplied data. Check the mirrored repository and CommonsWare project terms before redistribution, commercial use, CI integration, or modification of the kover-gate-report definition.

What prerequisites does kover-gate-report require?

You need an Android or Kotlin Multiplatform codebase, existing tests, and Kover coverage configured enough for a gate to evaluate results. The manifest assumes test edits trigger coverage review; it does not list build system versions, environment variables, or external services.