git-conventions
Apply this repo's git conventions when staging and committing: use targeted `git add` (never `git add -A`), group changes logically, and write conventional commit messages (type: description, imperative mood). Use when the user asks to commit, stage, or write a commit message in this repo. Do not use for branch/PR review workflows.
Best use case
git-conventions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply this repo's git conventions when staging and committing: use targeted `git add` (never `git add -A`), group changes logically, and write conventional commit messages (type: description, imperative mood). Use when the user asks to commit, stage, or write a commit message in this repo. Do not use for branch/PR review workflows.
Teams using git-conventions should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-conventions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-conventions Compares
| Feature / Agent | git-conventions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply this repo's git conventions when staging and committing: use targeted `git add` (never `git add -A`), group changes logically, and write conventional commit messages (type: description, imperative mood). Use when the user asks to commit, stage, or write a commit message in this repo. Do not use for branch/PR review workflows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git conventions
## Staging
- Always use **targeted** `git add <paths>` then commit. **Do not** use `git add -A`.
- Assume the working directory may contain things the user does not want committed.
- Use `git status` and group changes together logically.
- If the user asks you to commit, commit your changes. If there are unrelated changes, notify the engineer that you didn't commit those (but don't ask approval to proceed with the targeted commit) unless there's a genuine merge conflict serious enough to require attention.
## Commit messages
Conventional format — `<type>: <description>` in imperative present tense ("add feature", not "added feature"), first line ≤ 50 chars.
Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`, `ci`.
For full details (body/footer format, emoji prefixes, ticket-reference rules, non-ticket repos like this one), read [references/commit-conventions.md](./references/commit-conventions.md).Related Skills
alias:: [[Skills]]
No description provided.
rulesync
Rulesync CLI tool documentation - unified AI rule file management for various AI coding tools
logseq-youtube-notes
Format a YouTube video transcript inside a Logseq page into clean, navigable, timestamped Logseq-Flavored Markdown. Use when the user pastes a raw YouTube transcript, asks to organize/clean up video notes, add clickable {{youtube-timestamp}} headings, or structure a {{video ...}} block's notes. Do not use for non-video transcripts or for general LFM formatting (that is the logseq-lfm skill / logseq-core rule).
logseq-table-formatter
Format markdown tables inside Logseq Flavored Markdown (LFM) pages and journals: bullet-wrapped first row, continuation rows with aligned pipe columns, padded cells for readable plain text, and [[wikilinks]] for graph commands or pages when they exist. Use when adding or fixing tables in pages/*.md or journals/*.md, when the user asks for column alignment, or after editing comparison tables. Do not use to convert wide tables to bullets (skill logseq-convert-md-to-lfm) or for non-Logseq markdown.
logseq-slides
Author or fix Logseq slideshow pages where top-level bullets are section titles (H2) and nested bullets are individual slides with bullet points and a 16:9 image. Use when the user asks to build a slide deck/presentation in Logseq, add slides, or fix slide structure/image sizing. Do not use for ordinary page bullets or non-slide content.
logseq-question
Log a research question in the Logseq garden under Topic/Q/..., deduplicate against existing ___Q___ pages, add today's journal link, and research an answer (with AI attribution). Use when the user invokes /logseq-question or asks to file, record, or capture a scoped question page. Do not use for non-Q pages, general notes, or entity types other than question—use skill logseq-entity and the relevant [[Logseq/Entity/<Type>]] page instead.
logseq-pref
Load [[Logseq/Pref]] and linked pages for encode-wide garden preferences (page naming, namespaces, editorial defaults) before creating pages or entity types. Use when aligning new titles with [[Logseq/Pref/Page/Name]], refreshing prefs in-graph, or routing alongside logseq-entity for naming—not for per-entity definitions (those stay on [[Logseq/Entity/<Type>]]).
logseq-link-hygiene
Check, resolve, and normalize Logseq wikilinks before or after editing graph pages. Use when adding links, importing notes, creating pages, reviewing unresolved references, preventing accidental stub pages, or replacing newly invented wikilinks with canonical existing pages or aliases. Applies to all Logseq graph work, not only entity pages.
logseq-lfm
Look up Logseq-Flavored Markdown details beyond the always-on core: footnote syntax, nested fenced code blocks, bold-vs-backtick rendering pitfalls, the singular/plural naming rationale and aliases, the file-name-vs-link reference table, and the logical-vs-on-disk page distinction. Use when formatting footnotes, debugging why a ref/inline-code renders wrong, deciding a page name, or checking whether a page exists before creating a file. Baseline LFM rules live in logseq-core.
logseq-forum-post
Import and structure a forum post (Cursor Forum, Reddit, Stack Overflow, or other forums) into a Logseq page with title link, metadata, Original Poster / Response / Related / My Notes sections, and site-specific user namespaces. Use when the user pastes a forum thread or asks to capture/import a forum discussion. For person hubs use the logseq-person command and logseq-entity skill. Do not use for blog posts/articles (logseq-import-blog) or non-forum content.
logseq-flashcard
Create or maintain Logseq SRS flashcards and first-class Card entity pages in this garden. Use when the user asks to add a flashcard, factor out cards, create or audit Card pages, audit or fix Keyshort flashcards, ensure {{cards}} queries pick up cards, design or debug simple or advanced query expressions for card decks, or convert shortcut notes into review cards. New generic card work uses [[Card]] and [[Logseq/Entity/Card]]; legacy Keyshort audits may still encounter #card / [[card]]. Do not use for non-Logseq decks (e.g. repeater-only formats).
logseq-flashcard-favorite
Generate and keep in sync the [[Logseq/Flashcard/Review/Favorite]] deck tree from the graph's :favorites (logseq/config.edn). Use when the user asks to build, refresh, or reconcile favorite-driven flashcard decks: an aggregate {{cards (or …)}} deck, a negated background {{cards (not (or …))}} deck, and one scoped {{cards [[Favorite]]}} subpage per favorite. Runs idempotently via the mise file task and preserves the review-history children Logseq appends to {{cards}} blocks. Do not use for ad-hoc card authoring (logseq-flashcard) or non-favorite decks.