Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

release-engine

Étoiles22

Forks6

Mis à jour9 juillet 2026 à 15:52

Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

igmarin

igmarin/rails-agent-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

5 fichiers

SKILL.md

readonly

name	release-engine
type	atomic
license	MIT
description	Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build .gemspec && gem push --dry-run .gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
metadata	{"version":"1.0.0","user-invocable":"true"}

Release Engine

Use this skill when the task is to ship a Rails engine as a gem or prepare a new version.

Quick Reference

Bump	When to use	Action
Patch	Bug fixes and internal changes without public behavior breakage	Update version constant, document under Fixed
Minor	Backward-compatible features and new extension points	Update version constant, document under Added/Changed
Major	Breaking changes to API, setup, routes, migrations, config, or supported framework versions	Update version constant, document under Changed/Deprecated; write explicit upgrade notes

HARD-GATE

DO NOT release without updating CHANGELOG and version file.

Core Process

Confirm scope and compatibility impact — is this patch, minor, or major?
Run full test suite: bundle exec rspec. Fix all failures before proceeding.
Set the version bump — update the version constant once: module MyEngine; VERSION = "1.2.0"; end in lib/my_engine/version.rb.
Update changelog and upgrade notes.
Verify gemspec metadata and dependencies match tested Rails/Ruby versions.
Dry-run the gem build: gem build *.gemspec && gem push --dry-run *.gem. Verify contents.
Confirm installation docs and README match the release — update if needed.
Publish: gem push *.gem.

Extended Resources

Load release assets conditionally and say which one informed the output:

Read assets/release_checklist.md when producing the release verification checklist or quality gates.
Read assets/release_notes_template.md when drafting GitHub release notes, a long-form announcement, or public release copy.
Read assets/examples.md only when the user needs concrete release examples.

Changelog Guidelines

Document user-visible changes, not commits; group by Added/Changed/Fixed/Deprecated.
For deprecations, document removal plan and replacement; keep deprecated code for at least one minor cycle.
If the engine requires host changes during upgrade, document them explicitly even if the version bump is minor.

Examples

## [1.2.0] - 2024-03-15
### Added
- `widget_count` config option to limit dashboard widgets (default: 10).
### Changed
- Minimum Rails version is now 7.0.

Output Style

Version bump — patch/minor/major with explicit reasoning.
Version constant — updated lib/[engine_name]/version.rb.
CHANGELOG entries — under Added/Changed/Fixed/Deprecated headers.
Upgrade notes — host app steps (config, migrations, dependencies).
Gemspec + test status — metadata, files, dependency ranges confirmed; pass/fail result of bundle exec rspec.
Dry-run output — exact command gem build *.gemspec && gem push --dry-run *.gem plus contents verification (tar tf pkg/*.gem or gem contents).
Asset usage — state which of assets/release_checklist.md, assets/release_notes_template.md, assets/examples.md was loaded, or explicitly say none was needed.
GitHub release notes — concise draft with summary, highlights, upgrade notes, and verification status.
Release blockers — open issues, or explicitly "No blockers".

Integration

Skill	When to chain
document-engine	Updating README, setup instructions, or API docs for the release
upgrade-engine	Verifying Rails/Ruby version support or deprecation impact
test-engine	Ensuring tests pass before release and match documented behavior

Plus depuis ce dépôt

même dépôt

rails-agent-skills

igmarin/rails-agent-skills

Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.

2026-07-2122

security-check

igmarin/rails-agent-skills

Rails security audit with hard gates: NEVER reproduce credentials, tokens, API keys, or secrets verbatim in output — flag secrets by file path and line number only. Use when the user asks for a security audit, vulnerability scan, security review, or penetration test of a Rails application, or asks to check for XSS, CSRF, SSRF, SQL injection, open redirects, secrets exposure, authentication flaws, or authorization bypasses. Must check authentication/authorization, parameter handling, redirects/rendering, file/network/job inputs, and secrets/logging, verify each finding is exploitable with a concrete attack scenario before reporting (excluding false positives without using representative file paths), and present sections in the exact order specified, even if empty. Code review for XSS, CSRF, SSRF, SQL injection, open redirects, secrets.

2026-06-1522

create-engine-installer

igmarin/rails-agent-skills

Use when creating install generators or initializer installers for Rails engines — must use idiomatic Rails Thor generator commands, and follow the strict workflow: GENERATE (run generator against clean host app), VERIFY (check output files exist in correct host paths), RERUN (run a second time confirming idempotent output), TEST (write a minimal rerun spec that must always pass), and DOCUMENT (list what was generated versus what the user must do manually). Idempotent setup, host-app onboarding, and route mount setup. Trigger words: install generator, mountable engine setup, gem installation, engine onboarding, copy migrations, initializer generator.

2026-06-1522

create-engine

igmarin/rails-agent-skills

Use when creating or refactoring a Rails engine — must keep a narrow purpose and small public API, verify that a dummy app exists under spec/dummy or test/dummy, define the host-app contract specifying what the host must provide and what the engine exposes, create the minimal engine structure verifying that bundle exec rake inside the engine passes, and write minimum integration coverage through the dummy app. Covers namespace isolation, file structure, engine scaffolding, mountable engine setup, and Rails plugin scaffolding.

2026-06-1522

document-engine

igmarin/rails-agent-skills

Use when documenting Rails engines — show the minimum working install path first (gem add→bundle→install generator→mount in routes), document ALL configuration options with defaults (required vs optional), state host model/auth assumptions explicitly, keep examples copyable, satisfy minimum install path + config options + host assumptions before optional sections, validate against CHECKLIST.md with at least one copyable code example per section before finalizing. Generates README templates, installation guides, configuration docs, mount instructions, extension API docs, and migration notes. Trigger words: engine README, installation guide, configuration docs, mount instructions, migration notes, host integration examples.

2026-06-1522

test-engine

igmarin/rails-agent-skills

Use when writing and configuring RSpec tests for Rails engines — must ensure that a dummy app exists for testing, add the smallest integration test that proves mounting and boot and verify it passes before continuing, and run the full test suite via bundle exec rspec to verify all specs pass. Key capabilities: request and routing specs with namespace scoping, generator idempotency, configuration testing.

2026-06-1522

name	release-engine
type	atomic
license	MIT
description	Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build .gemspec && gem push --dry-run .gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
metadata	{"version":"1.0.0","user-invocable":"true"}

Release Engine

Use this skill when the task is to ship a Rails engine as a gem or prepare a new version.

Quick Reference

Bump	When to use	Action
Patch	Bug fixes and internal changes without public behavior breakage	Update version constant, document under Fixed
Minor	Backward-compatible features and new extension points	Update version constant, document under Added/Changed
Major	Breaking changes to API, setup, routes, migrations, config, or supported framework versions	Update version constant, document under Changed/Deprecated; write explicit upgrade notes

HARD-GATE

DO NOT release without updating CHANGELOG and version file.

Core Process

Confirm scope and compatibility impact — is this patch, minor, or major?
Run full test suite: bundle exec rspec. Fix all failures before proceeding.
Set the version bump — update the version constant once: module MyEngine; VERSION = "1.2.0"; end in lib/my_engine/version.rb.
Update changelog and upgrade notes.
Verify gemspec metadata and dependencies match tested Rails/Ruby versions.
Dry-run the gem build: gem build *.gemspec && gem push --dry-run *.gem. Verify contents.
Confirm installation docs and README match the release — update if needed.
Publish: gem push *.gem.

Extended Resources

Load release assets conditionally and say which one informed the output:

Read assets/release_checklist.md when producing the release verification checklist or quality gates.
Read assets/release_notes_template.md when drafting GitHub release notes, a long-form announcement, or public release copy.
Read assets/examples.md only when the user needs concrete release examples.

Changelog Guidelines

Document user-visible changes, not commits; group by Added/Changed/Fixed/Deprecated.
For deprecations, document removal plan and replacement; keep deprecated code for at least one minor cycle.
If the engine requires host changes during upgrade, document them explicitly even if the version bump is minor.

Examples

## [1.2.0] - 2024-03-15
### Added
- `widget_count` config option to limit dashboard widgets (default: 10).
### Changed
- Minimum Rails version is now 7.0.

Output Style

Version bump — patch/minor/major with explicit reasoning.
Version constant — updated lib/[engine_name]/version.rb.
CHANGELOG entries — under Added/Changed/Fixed/Deprecated headers.
Upgrade notes — host app steps (config, migrations, dependencies).
Gemspec + test status — metadata, files, dependency ranges confirmed; pass/fail result of bundle exec rspec.
Dry-run output — exact command gem build *.gemspec && gem push --dry-run *.gem plus contents verification (tar tf pkg/*.gem or gem contents).
Asset usage — state which of assets/release_checklist.md, assets/release_notes_template.md, assets/examples.md was loaded, or explicitly say none was needed.
GitHub release notes — concise draft with summary, highlights, upgrade notes, and verification status.
Release blockers — open issues, or explicitly "No blockers".

Integration

Skill	When to chain
document-engine	Updating README, setup instructions, or API docs for the release
upgrade-engine	Verifying Rails/Ruby version support or deprecation impact
test-engine	Ensuring tests pass before release and match documented behavior