AI-powered git commits using Claude Code CLI
A zsh function that analyzes your staged and unstaged changes, then creates logical, atomic commits following the Conventional Commits specification.
When you run smart-commit, Claude will:
AI-powered git commits using Claude Code CLI
A zsh function that analyzes your staged and unstaged changes, then creates logical, atomic commits following the Conventional Commits specification.
When you run smart-commit, Claude will:
Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:
| name | appsec-guardian |
|---|---|
| description | Expert Application Security Engineer. Prevents insecure code from reaching remote repositories by enforcing OWASP Top 10 and secure SDLC practices. Runs before git push to block vulnerable code. |
| tools | view, bash_tool, str_replace, create_file, web_search, web_fetch |
| model | inherit |
You are a senior Application Security Engineer with deep expertise in OWASP Top 10, secure SDLC, and security-by-design principles.
| import Database from 'better-sqlite3'; | |
| import { createDatabaseClient } from './proxy.ts'; | |
| // 1) Create an in-memory DB and your table(s). | |
| const db = new Database(':memory:'); | |
| db.exec(` | |
| CREATE TABLE users ( | |
| id TEXT PRIMARY KEY, | |
| data JSON | |
| ); |
One of my colleagues shared an article on writing (good) Git commit messages today: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
This deployment guide covers the steps required to install and configure a single HashiCorp Vault cluster as defined in the Vault Reference Architecture.
Below are instructions for installing and configuring Vault on Linux hosts running the systemd system and service manager.
This deployment guide is designed to work in combination with the Vault Reference Architecture and Consul Deployment Guide. Although not a strict requirement to follow the Vault Reference Architecture, please ensure you are familiar with the overall architecture design; for example installing Vault on multiple physical or virtual (with correct anti-affinity) hosts for high-availability and using Consul for the HA and storage backend.
| workflow "Demo workflow" { | |
| on = "push" | |
| resolves = ["SNS Notification"] | |
| } | |
| action "Build Image" { | |
| uses = "actions/docker/cli@c08a5fc9e0286844156fefff2c141072048141f6" | |
| runs = ["/bin/sh", "-c", "docker build -t $IMAGE_URI ."] | |
| env = { | |
| IMAGE_URI = "xxxxxxxx.dkr.ecr.ap-northeast-1.amazonaws.com/github-action-demo:latest" |
| #Requires -RunAsAdministrator | |
| #Requires -Version 5.0 | |
| # requires Windows 10 | |
| Get-EtwTraceProvider | Select-Object SessionName, Guid | sort SessionName | |
| # as Markdown | |
| <# | |
| #Requires -RunAsAdministrator | |
| $result = Get-EtwTraceProvider | sort SessionName | |
| $result | %{"|Name|GUID|";"|----|----|";}{"|$($_.SessionName)|$($_.Guid)|"} | |
| #> |
curl to get the JSON response for the latest releasegrep to find the line containing file URLcut and tr to extract the URLwget to download itcurl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \