Skip to content

Instantly share code, notes, and snippets.

View aaronedev's full-sized avatar

Aaron aaronedev

View GitHub Profile
@aaronedev
aaronedev / sync-upstream.yml
Created November 3, 2025 08:26
sync workflow github fork from upstream
# yamllint disable rule:truthy
# yamllint disable rule:document-start
name: Sync Upstream
on:
schedule:
- cron: "0 5 * * 0"
workflow_dispatch:
jobs:
call plug#begin(~/.vim/plugged)
" Core + quality of life
Plug tpope/vim-sensible
Plug tpope/vim-abolish
Plug jdhao/better-escape.vim " Escape insert mode with jk/kk etc.
" Indentation detection
Plug tpope/vim-sleuth " Automatically detect file indent settings
@aaronedev
aaronedev / Git_Commit_Freeze_Solution.md
Created September 30, 2025 11:57 — forked from bahadiraraz/Git_Commit_Freeze_Solution.md
Git Commit Freeze Due to GPG Lock Issues (Solution)

Git Commit Freeze Due to GPG Lock Issues

If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.

Solution Steps

1. Check for GPG Lock Messages

Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.

@aaronedev
aaronedev / tte.py
Created September 21, 2025 11:25
TerminalTextEffects (TTE) previewer script with adjustable options to cycle through all available options
#!/usr/bin/env python3
"""
Author: Aaron-Samuel Hauck
GitHub: https://github.com/aaronedev
Email: code@hyprland.de
License: MIT License
description:
tte cycle controller with reliable stdin and top-right overlay.
Converted from Bash. Adds interactive live controls, helpers, and options.
-- =============================================================================
-- lightline to lualine theme converter
-- Author: shadman
-- License: MIT License
-- =============================================================================
-- Instructions
-- 1. Source this file in neovim with lightline installed
-- 2. execute :lua light2lualine_theme_converter('theme_name')
@aaronedev
aaronedev / root_bash_profile.sh
Last active September 6, 2025 08:49
root bashrc_profile
#!/usr/bin/env bash
# ━━━━━━━━━━━━━━━━━━━━━ Root Bash Profile ━━━━━━━━━━━━━━━━━━━━━
# Source .bashrc if it exists and we're in an interactive shell
if [[ -f ~/.bashrc ]] && [[ $- == *i* ]]; then
source ~/.bashrc
fi
# Add /root/.local/bin to PATH if it exists
[[ -d /root/.local/bin ]] && export PATH="/root/.local/bin:$PATH"
@aaronedev
aaronedev / root_bashrc.sh
Created September 6, 2025 08:48
root bashrc
#!/usr/bin/env bash
# ━━━━━━━━━━━━━━━━━━━━━ Minimal Root Bashrc ━━━━━━━━━━━━━━━━━━━━━
# Minimal bash configuration for root based on user setup
# Test for an interactive shell
[[ $- != *i* ]] && return
[[ -z "$PS1" ]] && return
# Source system bashrc
if [[ -f /etc/bashrc ]]; then
@aaronedev
aaronedev / virtualenv_direnv.sh
Created September 6, 2025 07:52
automatically source venv using direnv
# .envrc β€” prefer `workon py_env`, fallback to common venv locations
project_env='py_env'
# if workon is already available, use it
if type workon >/dev/null 2>&1; then
workon "$project_env"
return
fi
# try to source virtualenvwrapper to get workon
@aaronedev
aaronedev / post-commit-remotes
Last active September 26, 2025 09:00
post-commit hook to push to all other remotes defined like codeberg or gitlab for example
#!/bin/bash
# Post-commit hook to automatically push to GitLab and Codeberg after local commits
# This runs after each local commit
#
# Toggle remotes by setting environment variables:
# PUSH_GITLAB=false git commit -m "message" # Disable GitLab push
# PUSH_CODEBERG=false git commit -m "message" # Disable Codeberg push
# PUSH_REMOTES=false git commit -m "message" # Disable all remote pushes
#

CLAUDE.md - Universal Development Principles

This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.

Required Tools and Research Methods

1. Mandatory MCP Tool Usage

BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.