Skip to main content
hegeldev
Profil créateur GitHub

hegeldev

Vue par dépôt de 22 skills collectés dans 8 dépôts GitHub.

skills collectés
22
dépôts
8
mis à jour
13 août 2026
explorateur de dépôts

Dépôts et skills représentatifs

coverage
Analystes en assurance qualité des logiciels et testeurs

How to approach code coverage in this project. Use when coverage CI fails, when writing tests for new code, when deciding whether to add // nocov, or when you need to make untestable code testable. Also use proactively when writing new code to ensure it will…

20 juil. 2026
add-library-support
Développeurs de logiciels

How to add hegel-rust support for a third-party Rust crate. Use when the user asks to 'add support for <crate>', 'add a <crate> integration', 'add generators for <crate>', or similar. Orchestrates implementing a generator and DefaultGenerator impl for every…

6 juil. 2026
new-generator
Développeurs de logiciels

How to add a new generator to hegel-rust. Use when the user asks to implement, add, or write a generator for a type — e.g. 'add a generator for Url', 'implement a UUID generator', 'write a generator for jiff::civil::Date'. Covers the generator struct, builder…

6 juil. 2026
changelog
Développeurs de logiciels

Changelog style guide for writing RELEASE.md files. Use when creating or reviewing RELEASE.md, writing changelog entries, or preparing a PR that needs release notes.

6 juil. 2026
new-default-generator
Développeurs de logiciels

How to add a DefaultGenerator impl for a type so gs::default::<T>() works. Use when the user asks to wire up default() for a type, add a default generator, or make a type usable with #[derive(DefaultGenerator)]. Pair after the new-generator skill when adding…

6 juil. 2026
self-review
Analystes en assurance qualité des logiciels et testeurs

Review your own changes before creating a pull request. Use this before running create-pr, or whenever you want to check that your changes are clean, correct, and well-tested. Trigger when: about to create a PR, finished a chunk of work, or asked to review…

12 mai 2026
align-libhegel
Développeurs de logiciels

How to align the Go FFI wrapper to a new libhegel (hegel-c) release. Use after bumping the pinned libhegel version (internal/libhegel/version.go, via `just vendor-libhegel`), when `just check` fails with a symbol-resolution or version-mismatch error against…

14 juil. 2026
changelog
Développeurs de logiciels

Changelog style guide for writing RELEASE.md files. Use when creating or reviewing RELEASE.md, writing changelog entries, or preparing a PR that needs a changelog.

9 juil. 2026
go-concurrency
Développeurs de logiciels

Go concurrency patterns and pitfalls for this codebase. Use when writing or reviewing code that involves goroutines, channels, mutexes, shared state, subprocess management, or anything that runs concurrently. Also use proactively when writing new code — ask…

2 avr. 2026
coverage
Analystes en assurance qualité des logiciels et testeurs

How to approach code coverage in this project. Use when coverage CI fails, when writing tests for new code, when deciding whether to add // coverage-ignore, or when you need to make untestable code testable. Also use proactively when writing new code to…

2 avr. 2026
self-review
Analystes en assurance qualité des logiciels et testeurs

Review your own changes before creating a pull request. Use this before running create-pr, or whenever you want to check that your changes are clean, correct, and well-tested. Trigger when: about to create a PR, finished a chunk of work, or asked to review…

2 avr. 2026
8 dépôts affichés sur 8
Tous les dépôts sont affichés