igmarin/build
build/SKILL.md
Writes implementation code, runs test suites, and validates changes against acceptance criteria for a pre-planned task. Use this skill when the 'Research' and 'Strategy' phases are complete and you are ready to apply a single, well-defined code change. Trigger words: implement task from plan, execute planned change, fix bug in task, add test for task, build feature slice.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills buildInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 2:22 AM151.9s1 file scanned
SKILL.md
- name:
- build
- license:
- MIT
- description:
- >
- well-defined code change. Trigger words:
- implement task from plan, execute
- version:
- 1.0.0
- user-invocable:
- true
- argument-hint:
- <task reference or description> e.g. 'Task 2 from user-auth' or 'add rate limiting to the API'
Build
Quick Reference
Use only after a task is already planned.
Write/adjust the failing test first -> run it -> verify the right failure -> implement -> rerun -> report verification.
Keep the change scoped to the named task; call out any blocked or skipped checks.
HARD-GATE: Tests Gate Implementation
Implementation code CANNOT be written until:
1. The relevant test exists or has been updated
2. The test has been run
3. The test fails for the expected task-related reason
When to use
Use for a single planned implementation task; use planning/review skills for broad design, task creation, or large refactors.
Core Process
- Read: Review the pre-defined task, spec, and relevant code. Stop and clarify if the scope is vague or exceeds a single task.
- Implement: Apply the smallest useful code change that satisfies the task requirements.
- Verify:
- TDD: Write/update tests for new behavior or bug fixes.
- Reproduction: For bugs, confirm the failure with a test before fixing.
- Full Suite: Run the strongest available project checks (e.g.
bundle exec rspec) to prevent regressions. - Manual Check: Perform task-specific verification (e.g.,
curlan endpoint or check logs).
- Final Gate: Confirm behavior matches the task, no unrelated scope was added, and all tests pass.
See EXAMPLES.md for compact TDD and bug-fix examples.
Rules
- Honest Verification: If a critical check could not be run, state it clearly.
Output Style
Report: task completed, tests-first evidence, implementation summary, verification commands/results, and residual risk.
Integration
| Skill | When to chain | |-------|---------------| | plan-tests | When the task lacks a clear first failing spec | | write-tests | When test structure or examples are needed | | code-review | After implementation and verification pass |
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
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.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
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.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026