kryota-dev/code-change-verification
.agents/skills/code-change-verification/SKILL.md
Run the mandatory verification stack (lint + test) when changes affect shell scripts, zsh config, Makefile, or CI config. Skip when only documentation files are changed. Report results and prompt for fixes on failure.
development
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add kryota-dev/dotfiles code-change-verificationInstall 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: Apr 15, 2026, 1:09 PM6.9s1 file scanned
SKILL.md
- name:
- code-change-verification
- description:
- >-
- user-invocable:
- true
- allowed-tools:
- Bash
Code Change Verification
Run the mandatory verification stack for the dotfiles repository.
Steps
1. Identify changed files
# Working tree and staging changes
git diff --name-only
git diff --cached --name-only
# All branch changes (including already committed)
git diff --name-only main...HEAD 2>/dev/null
2. Check if changes are documentation-only
If all changed files are .md files, skip verification and report:
Verification skipped: only documentation (.md) files were changed — lint/test not required.
3. Run the verification stack
If code changes are present, run the following in order:
# lint (shellcheck + shfmt + zsh syntax check)
make lint
# test (lint + bats)
make test
4. Report results
On success
Verification passed: all lint and test checks passed.
On failure
Report the error output and suggest fixes:
Verification failed:
- make lint: {pass/fail}
- make test: {pass/fail}
Error details:
{error output}
Suggested fix:
{specific fix proposal}
Notes
make fmt(auto-fix) is intentionally excluded. Auto-fix should be run explicitly by the user.- Verification commands reference Makefile targets. If the command structure changes, only the Makefile needs to be updated.
Related Skills
kryota-dev/cc-code-review
development
VerifiedTrustedCommunity
`cc-code-review` エージェントを起動して独立したコンテキストでコードレビューを実行する。 現在のセッションのバイアスのないフレッシュな視点で、プロジェクトの CLAUDE.md を踏まえたレビューを行う。 トリガー: "cc-code-review", "ccでレビュー", "別の視点でレビュー", "セカンドオピニオン" 使用場面: (1) PRのコードレビュー (2) ブランチ差分のレビュー (3) 特定ファイルのレビュー (4) 現在の変更のレビュー
1SKILL.mdUpdated Jun 5, 2026
kryota-dev/wtp
tools
VerifiedTrustedCommunity
Comprehensive guide for the `wtp` (Worktree Plus) CLI by satococoa — an enhanced Git worktree manager. Use this whenever the user wants to create, list, remove, or navigate Git worktrees with wtp, mentions `wtp add`/`wtp cd`/`wtp list`/`wtp remove`/`wtp exec`, asks about automatic worktree paths from branch names, post-create hooks (copy/symlink/command) in `.wtp.yml`, branch tracking for worktrees, or shell integration (`wtp shell-init`, `wtp hook`, tab completion, auto-cd). Trigger this even when the user just describes the workflow — e.g. 'spin up a worktree for this feature branch', 'jump to my auth worktree', 'clean up the worktree and its branch' — without naming wtp explicitly, as long as wtp is the available tool.
1SKILL.mdUpdated Jun 4, 2026
kryota-dev/supabase
tools
VerifiedTrustedCommunity
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).
1SKILL.mdUpdated Jun 4, 2026
kryota-dev/supabase-postgres-best-practices
data-ai
VerifiedTrustedCommunity
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
1SKILL.mdUpdated Jun 4, 2026