Run any Skill in Manus with one click

do-work-rails

Stars16

Forks0

UpdatedJuly 10, 2026 at 16:15

Execute a discrete unit of work in end-to-end: plan, implement, validate via rubocop and the full test suite, then commit. Use when the user asks to do work, implement, build, fix, or ship a task in this project, or implement a phase from a given plan.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

meleu

meleu/.dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	do-work-rails
description	Execute a discrete unit of work in end-to-end: plan, implement, validate via rubocop and the full test suite, then commit. Use when the user asks to do work, implement, build, fix, or ship a task in this project, or implement a phase from a given plan.

do-work

A unit of work in this repo follows the following phases (do not skip phases, do not reorder them):

0. Understand the task

Read any referenced plan or PRD.
Explore the codebase to understand the relevant files, patterns, and conventions.
If the task is non-trivial or ambiguous, ask the user to clarify scope before proceeding.
Restate the task in one sentence so the goal is explicit.

1. Plan (optional)

If the task has not already been planned, create a plan for it.

2. Implement

Work through the plan step by step.
Add tests alongside the code change.

3. Feedback loops

Run both checks and fix every issue they report. Do not commit with failures.

bundle exec rubocop -a
bin/rails test:all

4. Commit

Once both loops are green, commit the work.

More from this repository

same repository

bash-coding-standards

meleu/.dotfiles

Bash coding standards for production-grade scripts. Use whenever writing, reviewing, or refactoring Bash scripts/functions; whenever conducting a Bash code review; or whenever bash coding standards are referenced.

2026-07-1616

git-learning-notes

meleu/.dotfiles

Study a project's commit history as a tutor, teaching the techstack (frameworks, idioms, tooling, conventions). Use when user wants to learn a project's stack from git history or mentions git-learning-notes.

2026-07-1016

grill-me

meleu/.dotfiles

A relentless interview to sharpen a plan or design.

2026-07-1016

prd-to-plan

meleu/.dotfiles

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

2026-07-1016

write-a-prd

meleu/.dotfiles

Create a PRD through user interview, codebase exploration, and module design. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

2026-07-1016

name	do-work-rails
description	Execute a discrete unit of work in end-to-end: plan, implement, validate via rubocop and the full test suite, then commit. Use when the user asks to do work, implement, build, fix, or ship a task in this project, or implement a phase from a given plan.

do-work

A unit of work in this repo follows the following phases (do not skip phases, do not reorder them):

0. Understand the task

Read any referenced plan or PRD.
Explore the codebase to understand the relevant files, patterns, and conventions.
If the task is non-trivial or ambiguous, ask the user to clarify scope before proceeding.
Restate the task in one sentence so the goal is explicit.

1. Plan (optional)

If the task has not already been planned, create a plan for it.

2. Implement

Work through the plan step by step.
Add tests alongside the code change.

3. Feedback loops

Run both checks and fix every issue they report. Do not commit with failures.

bundle exec rubocop -a
bin/rails test:all

4. Commit

Once both loops are green, commit the work.