Albert Fougy albertfougy

Gemini CLI: Explain Mode

You are Gemini CLI, operating in a specialized Explain Mode. Your function is to serve as a virtual Senior Engineer and System Architect. Your mission is to act as an interactive guide, helping users understand complex codebases through a conversational process of discovery.

Your primary goal is to act as an intelligence and discovery tool. You deconstruct the "how" and "why" of the codebase to help engineers get up to speed quickly. You must operate in a strict, read-only intelligence-gathering capacity. Instead of creating what to do, you illuminate how things work and why they are designed that way.

Your core loop is to scope, investigate, explain, and then offer the next logical step, allowing the user to navigate the codebase's complexity with you as their guide.

Core Principles of Explain Mode

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:

Keybase proof

I hereby claim:

I am albertfougy on github.
I am albertfougy (https://keybase.io/albertfougy) on keybase.
I have a public key ASDWPn2o0fuJiHSyxa3I95iXady3A3-sm1hFxYKcSOFmoQo

To claim this, I am signing this object:

git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200

Initializing a vault:

vault init

Usage

(Create a symlink pytest for py.test)

pytest [options] [file_or_dir] [file_or_dir] ...

Help:

Postgres Cheatsheet

This is a collection of the most common commands I run while administering Postgres databases. The variables shown between the open and closed tags, "<" and ">", should be replaced with a name you choose. Postgres has multiple shortcut functions, starting with a forward slash, "". Any SQL command that is not a shortcut, must end with a semicolon, ";". You can use the keyboard UP and DOWN keys to scroll the history of previous commands you've run.

Setup

installation, Ubuntu

http://www.postgresql.org/download/linux/ubuntu/ https://help.ubuntu.com/community/PostgreSQL

Before we begin...

Each person open your terminal and enter the following:

git config --global alias.lg "log --oneline --all --graph --decorate"

This creates an "alias" so that the command git lg will actually translate to git log --oneline --all --graph --decorate, so you don't have to type it every time. This command prints out a very clean history of all the commits in your repo, including branches. Note: git log only works inside of a git repo, so continue with the drills below and use git lg to see your commit history.

	<!-- colocar esse snippet em %SUBLIMEINSTALLPATH%/Packages/docker-compose/docker-compose-template-v2.sublime-snippet -->

	<snippet>
	<content><![CDATA[
	version: '2'

	services:
	web:
	build: ./dir
	container_name: my-web-container

	import os
	import re
	import shutil
	import sys

	cmd_re = re.compile('(\w+)\s+.*')
	if 'zsh' in sys.argv[1]:
	cmd_re = re.compile(".;(\w+)\s+.")

	history= open(sys.argv[1], 'rb').read()

	#!/bin/bash
	#####################################################
	# Name: Bash CheatSheet for Mac OSX
	#
	# A little overlook of the Bash basics
	#
	# Usage:
	#
	# Author: J. Le Coupanec
	# Date: 2014/11/04