Git i control de versions
Operacions de Git, assistència per a commits i gestió de branques
dendritic-nix
sebnow
"Applies the Dendritic Pattern for structuring Nix flake configurations with flake-parts. Every file is a flake-parts module organized by feature (aspect), not by configuration class. Use when structuring Nix flakes, creating flake-parts modules, composing multi-host configs, organizing NixOS/home-manager/nix-darwin configuration, or sharing values across configuration classes. Triggers: nix flake structure, flake-parts modules, multi-host configs, aspect modules. Do NOT use for general Nix language questions, nixpkgs packaging, or NixOS module authoring unrelated to flake structure."
linux-phone-porting
angelwzr
Use for every hardware bring-up / debug session when porting mainline Linux to a phone. Enforces evidence-first debugging - capture device logs, then research across mainline, the vendor kernel, postmarketOS, Halium/UBports, Mobian and NixOS - before writing or flashing any fix. Requires an already-unlocked bootloader; locked devices are out of scope.
verify-translator
zotero
Steps that MUST be performed to verify a Zotero translator after every addition or modification, and before submitting a PR.
zig-0.15
zigcc
This skill provides Zig 0.15.x API guidance and should be used when writing or reviewing Zig code. It ensures correct usage of Zig 0.15 APIs, preventing common mistakes from using outdated 0.11/0.12/0.13/0.14 patterns. Essential for ArrayList, std.Io.Writer/Reader (Writergate), HTTP client, Ed25519, JSON, and type introspection APIs.
knowledge-site-creator
joeseesun
一句话生成任何领域的知识学习网站。AI自动理解主题、创作内容、生成页面、部署上线。适用于任何需要系统学习的知识领域：进化心理学、大模型术语、化学元素、历史事件等。
sdlc-yolo
uinaf
"ALL coding work. Features, fixes, refactors — never hand-code. Delegates to coding-agent, reviews, auto-merges or escalates."
issue-tree-builder
sruthir28
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.
Session Close
matiaszanolli
"End-of-session ritual — diff stated facts against ground truth and propose synchronised edits across ROADMAP.md / HISTORY.md / README.md"
posting-bitwarden-review-comments
bitwarden
Use this skill when posting inline comments to GitHub pull requests. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions. Use after findings are classified and ready to post. DO NOT USE when posting summary comments.
analyzing-git-sessions
bitwarden
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
commit
vinta
Use when completing an implementation task, when the user asks to commit, or when changes span multiple concerns and need separate logical commits (structural vs behavioral vs config)
release-engine
drakulavich
Cuts a kesha-engine release (bare vX.Y.Z tag) per CLAUDE.md rules — pre-flight audits, engine-only version bump, annotated tag carrying the notes, draft validation with authenticated download, publish, then verify. Refuses to auto-run; user must explicitly invoke. Knows the workflow-frozen-at-the-tag trap, the gh-cli release-notes trap, and the draft-URL 404 trap. For a CLI release use release-cli.
gentle-ai-branch-pr
Gentleman-Programming
"Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review."
gentle-ai-chained-pr
Gentleman-Programming
"Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus."
commit
AsiaOstrich
"[UDS] Generate commit messages following Conventional Commits standard"
Testing Guide
AsiaOstrich
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT, 測試, 單元, 整合, 端對端.
release
AsiaOstrich
"[UDS] Guide release process and changelogs"
Documentation Guide
AsiaOstrich
Guide documentation structure, content requirements, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup, technical docs. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 說明文件, 技術文件.
review
AsiaOstrich
"[UDS] Perform systematic code review with checklist"
changelog
AsiaOstrich
"[UDS] Generate and maintain CHANGELOG.md entries"
ship-without-actions
hushh-labs
The complete release pipeline for when GitHub Actions is unavailable — runs every CI check, then deploys, as one command. Use when Actions runs sit queued or never start, when a deploy fails at "Validate deployment SHA against main", when someone says "GitHub Actions is down" / "deployment is down" / "runners are stuck", when asked to "run all the CI checks locally" or "verify before deploying", or when work must ship and the governed workflow cannot be scheduled.
ship-ios-testflight
hushh-labs
Compatibility entry point for shipping an explicitly authorized green-main iOS build to TestFlight through the governed GitHub workflow.
kg-feature-delivery
hushh-labs
Take a knowledge-graph feature prompt (a KG .html plus a long "implement X in One" prompt) from prompt to verified-live-on-UAT in one sitting, automation only. Use whenever Ankit hands over a feature graph and says "do this like we did for Circle / Connect / SMS / Profile". Encodes what actually worked on 2026-09-18..22 — measure the checkout before building, one failing test per graph observation, the repo's own patterns, an honest status vocabulary, and a ship loop that ends at the serving revision's deploy-sha, not at a green workflow.
release-ios-appstore
hushh-labs
Compatibility entry point for the canonical Hushh iOS App Store release skill. Use only when explicitly asked to prepare or submit an App Store release.