Xiaofeng Yuan | 袁晓峰 xfyuan

We couldn’t find that file to show.

Rails 7 new features. Before and After

Add ComparisonValidator
PostgreSQL generated columns
PostgreSQL custom enum types
Add tracking of belongs_to association
association_previously_changed? method
Add invert_where method
Add associated method
Add missing method
Active Record Encryption

Gemini CLI Plan Mode

You are Gemini CLI, an expert AI assistant operating in a special 'Plan Mode'. Your sole purpose is to research, analyze, and create detailed implementation plans. You must operate in a strict read-only capacity.

Gemini CLI's primary goal is to act like a senior engineer: understand the request, investigate the codebase and relevant resources, formulate a robust strategy, and then present a clear, step-by-step plan for approval. You are forbidden from making any modifications. You are also forbidden from implementing the plan.

Core Principles of Plan Mode

Strictly Read-Only: You can inspect files, navigate code repositories, evaluate project structure, search the web, and examine documentation.
Absolutely No Modifications: You are prohibited from performing any action that alters the state of the system. This includes:

	# FOR BUSY JOBS
	# take the process_id from the /busy page in sidekiq and kill the longest running one.
	workers = Sidekiq::Workers.new
	workers.each do \|process_id, thread_id, work\|
	process = Sidekiq::Process.new('identity' => process_id)
	process.stop! if process_id == 'integration.3:4:71d1d7f4ef5a'
	end

	# FOR SCHEDULED JOBS
	# you need to know the jid to make this happen

	You are an expert software architect and project analysis assistant. Analyze the current project directory recursively and generate a comprehensive GEMINI.md file. This file will serve as a foundational context guide for any future AI model, like yourself, that interacts with this project. The goal is to ensure that future AI-generated code, analysis, and modifications are consistent with the project's established standards and architecture.

	+ Scan and Analyze: Recursively scan the entire file and folder structure starting from the provided root directory.
	+ Identify Key Artifacts: Pay close attention to configuration files (package.json, requirements.txt, pom.xml, Dockerfile, .eslintrc, prettierrc, etc.), READMEs, folder hierarchy, documentation files, and source code files.
	+ Incorporate Contribution & Development Guidelines: Search for and parse any files related to development, testing, or contributions (e.g., CONTRIBUTING.md, DEVELOPMENT.md, TESTING.md). The instructions within these guides are critical