Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
owenlamont
Profil créateur GitHub

owenlamont

Vue par dépôt de 19 skills collectés dans 2 dépôts GitHub.

skills collectés
19
dépôts
2
mis à jour
2026-07-04
explorateur de dépôts

Dépôts et skills représentatifs

human-collaboration
Développeurs de logiciels

Write agent output for the accountable human reviewer — route narrative by audience and lifespan, lead with a budgeted summary, keep detail collapsed, and plan before building. Use when writing PR or issue descriptions, commit messages, or code comments, when addressing or resolving PR review comments, when deciding whether to raise an issue or where work-narrative belongs, or when scoping a non-trivial change before generating code.

2026-07-04
python-async
Développeurs de logiciels

Write asyncio Python to this project's standards — concurrent coroutines, async-all-the-way, and safe handling of errors from concurrent tasks. Use when writing async/await code, gathering coroutines, designing async FastAPI endpoints or clients, or handling failures from concurrent work.

2026-07-04
python-code-style
Développeurs de logiciels

Write Python source to this project's standards. Use when authoring or refactoring Python code and deciding on style, type hints, docstrings, comments, imports, or language idioms.

2026-07-04
python-datetime
Développeurs de logiciels

Work with dates, times, and timezones to this project's standards. Use when creating, parsing, serialising, comparing, or storing datetimes, or handling timezones.

2026-07-04
python-error-handling
Développeurs de logiciels

Handle errors in Python to this project's standards — custom domain exceptions, narrow catches, and failing fast. Use when raising or catching exceptions, writing try/except, designing an exceptions module, or deciding whether to swallow or propagate an error.

2026-07-04
python-libraries
Développeurs de logiciels

Reach for this project's preferred, well-supported libraries instead of hand-rolling. Use when choosing a library for HTTP, retries, JSON, or parsing, or whenever you are about to write something the standard library or a maintained package already does.

2026-07-04
python-lint-format
Développeurs de logiciels

Lint and format a Python project with the prek hook runner. Use when checking or cleaning the working tree, resolving lint/format/type/complexity/spelling failures, or understanding what each linter config enforces.

2026-07-04
python-pandas
Développeurs de logiciels

Write Pandas code to this project's standards — vectorised operations, Pandas-native types, and Pandera schemas. Use when importing or using pandas — transforming DataFrames or Series, handling missing values, or type-hinting tabular data.

2026-07-04
Affichage des 8 principaux skills collectés sur 10 dans ce dépôt.
release
Développeurs de logiciels

Use when cutting a ryl release. Covers the lockstep version bump across the five version-bearing files, the lockfile refresh, the tag/push gate, and the post-release SchemaStore + Trusted-Publishing flow.

2026-06-22
winget-defender-fp
Développeurs de logiciels

Use when a ryl winget-pkgs validation PR is blocked by a Microsoft Defender false positive (`Validation-Defender-Error` / "Installer failed security check"). Covers the transient-vs-reproducible decision, local Defender + VirusTotal reproduction, the WDSI false-positive submission, and the log noise to ignore.

2026-06-22
ryl
Développeurs de logiciels

Lint and auto-fix YAML with the ryl CLI (a fast, yamllint-compatible linter). Use when running or configuring ryl in a repo, fixing YAML lint errors, setting up YAML linting, or migrating from yamllint. Covers the no-default-on-rules gotcha (ryl exits 2 without a config), exit codes, --fix vs --diff, machine-readable output, the YAML-vs-TOML config split, inline directives, and YAML embedded in Markdown.

2026-06-22
filing-issues
Développeurs de logiciels

Use when filing or editing a GitHub issue/PR for ryl or, especially, for another project (yamllint, granit, SchemaStore). Covers the cross-repo reference footgun, the draft-locally-then-file gate for other people's repos, the never-on-an-assumption rule, and the verified-Sources requirement — so a published issue does not need a verify-then-re-push cycle.

2026-06-21
property-tests
Analystes en assurance qualité des logiciels et testeurs

Use when adding or changing a rule's detection or safe-fix behaviour, or editing any property-test suite (safe-fix / rule-checker / markdown-fix / config). Covers what each generator must be extended with, the ~1000x pre-commit run, and which rules intentionally have no safe `--fix`.

2026-06-21
codex-review
Développeurs de logiciels

Drive a Codex CI code review on a GitHub PR end to end, from triggering it through monitoring and classifying the verdict (clean / findings / rate-limited) to handling the resulting comments (react, resolve, reply). Use after pushing changes you want Codex to (re-)review, while waiting on a verdict, or when triaging Codex's review comments. It encodes the polling gotchas (REST not GraphQL, three verdict channels, transient 👀) and the comment-handling conventions (when to thumbs-up/down, resolve, or reply).

2026-06-21
coverage
Analystes en assurance qualité des logiciels et testeurs

Use when chasing missed lines/regions to satisfy CI's zero-missed-coverage gate, or writing tests to close uncovered ranges. Covers the coverage-missing.py workflow, coverage-friendly Rust idioms, and the common uncovered hotspots.

2026-06-21
retrospective
Développeurs de logiciels

Use to run a development-friction retrospective over recent Claude Code sessions: a cheap deterministic extractor digests the transcripts (tool errors, wall-clock waits, retry clusters, corrections), then a small number of classifier agents tag the digests against a fixed taxonomy. Prefer this over fanning a classifier agent at each raw transcript (far cheaper, less noise).

2026-06-21
Affichage des 8 principaux skills collectés sur 9 dans ce dépôt.
2 dépôts affichés sur 2
Tous les dépôts sont affichés