Skip to main content
在 Manus 中运行任何 Skill
一键导入
GitHub 仓库

lcstats_relay

lcstats_relay 收录了来自 aoirint 的 5 个 skills,并提供仓库级职业覆盖和站内 skill 详情页。

已收集 skills
5
Stars
0
更新
2026-07-26
Forks
0
职业覆盖
2 个职业分类 · 已分类 100%
仓库浏览

这个仓库中的 skills

flet-project-quality-check
软件开发工程师

Create, align, or review production-quality Python Flet applications across package and module architecture, presentation state, Flet controls, async lifecycle, persistence and I/O boundaries, semantic UI tests, Flet packaging, platform artifacts, security, and developer documentation. Use for new Flet projects, large UI refactors, Flet architecture alignment, target packaging, release readiness, or reviews of Flet application code. Pair with python-quality-check for uv, Ruff, mypy, pytest, coverage, Python packaging, and CI quality gates.

2026-07-26
python-quality-check
软件开发工程师

Create, align, or review strict uv-managed installable Python projects hosted on GitHub across packaging, dependency locking, Ruff, mypy, pytest, statement and branch coverage, distribution artifacts, and CI parity. Use for Python applications, libraries, or CLIs with pyproject.toml, .python-version, uv.lock, src/tests layouts, dependency changes, quality-gate adoption, packaging, or GitHub Actions validation; pair with a framework-specific Skill when one applies.

2026-07-26
apm-usage
其他计算机职业

Select a reviewed APM CLI version, then set up, pin, deploy, audit, and update APM-managed agent dependencies safely. Use when creating or editing apm.yml or apm.lock.yaml, choosing or installing APM, adding an Agent Skill, plugin, or MCP dependency, validating a pinned deployment, or preparing a cooldown-aware update proposal.

2026-07-26
github-workflow
软件开发工程师

Quality-check GitHub Actions workflows, repository issues, pull requests, and their comments. Use when creating, editing, reviewing, or documenting CI automation, issue text, PR text, reviews, replies, or squash merges.

2026-07-26
software-documentation-maintenance
软件开发工程师

Design, restructure, and maintain a software repository's documentation system, including its required docs/domain, docs/architecture, and docs/operations map, canonical ownership, technical evidence, indexes, links, and change synchronization. Use when creating or migrating developer docs, documenting system behavior or design decisions, establishing documentation rules, or reviewing repository-wide documentation completeness. Pair with prose-quality-check for wording and with a domain skill for specialized technical correctness.

2026-07-26