Skip to content

chore: updating git-kb .claude files - #36

Closed
mateodelnorte wants to merge 1 commit into
mainfrom
chore/adding-claude-files-3
Closed

mateodelnorte wants to merge 1 commit into
mainfrom
chore/adding-claude-files-3

Conversation

@mateodelnorte

@mateodelnorte mateodelnorte commented Feb 21, 2026 •

Copy link
Copy Markdown
Contributor

chore: updating git-kb .claude files

Summary by CodeRabbit

  • New Features

    • Added interactive workflows for core knowledge base operations: creating documents, starting tasks, logging progress, reviewing task completion, searching the knowledge base, closing completed work, and end-of-session handoffs.
  • Documentation

    • Updated GitKB terminology from "database-first knowledge base" to "distributed knowledge base."

.
chore: updating git-kb .claude files
@coderabbitai

coderabbitai Bot commented Feb 21, 2026 •

Copy link
Copy Markdown

Walkthrough

Added seven new KB command documentation files that define structured workflows for knowledge base operations: creating documents, starting tasks, logging progress, reviewing criteria, searching, closing tasks, and end-of-session handoff. Also updated terminology from "database-first" to "distributed knowledge base" in existing documentation.

Changes

Cohort / File(s) Summary
KB Command Documentation
.claude/commands/kb-create.md, .claude/commands/kb-start.md, .claude/commands/kb-progress.md, .claude/commands/kb-review.md, .claude/commands/kb-search.md, .claude/commands/kb-close.md, .claude/commands/kb-handoff.md
Seven new command definition files establishing workflows for KB operations: create (document generation with type-specific templates), start (task initiation with context loading), progress (logging work updates), review (criterion evaluation against codebase), search (querying KB), close (task completion with criteria verification), and handoff (end-of-session context capture).
Terminology Updates
.claude/skills/gitkb/SKILL.md, .kb/AGENTS.md
Replaced "database-first knowledge base" with "distributed knowledge base" in SKILL description and AGENTS reference documentation for consistency.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 Seven commands we hop to bring,
A workflow dance for everything!
From create to close, progress to start,
A distributed KB—a fuzzy work of art! 🌟

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: updating git-kb .claude files' is vague and does not clearly convey the scope or nature of the changes being made. Consider a more specific title that describes the actual changes, such as 'chore: add kb command documentation files' or 'chore: add kb workflows for task management and review'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/adding-claude-files-3

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Feb 21, 2026

Copy link
Copy Markdown

Greptile Summary

Adds comprehensive GitKB command documentation and updates terminology from "database-first" to "distributed" knowledge base. Seven new command files provide detailed workflows for task lifecycle management (create, start, progress, review, close), search, and session handoff.

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk
  • Documentation-only changes with no code modifications - adds new command documentation files and updates terminology consistently across two files
  • No files require special attention

Important Files Changed

Filename Overview
.claude/commands/kb-close.md New command added for closing tasks with verification - comprehensive workflow for task completion
.claude/commands/kb-create.md New command for creating KB documents with auto-incrementing slugs and context-aware content generation
.claude/commands/kb-handoff.md New command for session handoff - ensures all work-in-progress is committed and context is fresh
.claude/commands/kb-progress.md New command for logging progress on tasks - quick datestamped updates without full edit cycle
.claude/commands/kb-review.md New command for reviewing tasks against acceptance criteria and codebase state
.claude/commands/kb-search.md New command for searching the knowledge base with formatted results and suggested actions
.claude/commands/kb-start.md New command for starting work on tasks - loads context, sets status, and prepares workspace
.claude/skills/gitkb/SKILL.md Updated GitKB description from "database-first" to "distributed" knowledge base
.kb/AGENTS.md Updated GitKB description from "database-first" to "distributed" in two locations

Last reviewed commit: 2144603

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/commands/kb-handoff.md:
- Around line 74-89: Add a language specifier to the fenced code block starting
with the triple backticks that contains "## Session Handoff" (e.g., change the
opening ``` to ```text or ```md) so the code block passes MD040; update the
opening fence only and leave the block contents (the headings and list items
such as "### What Was Done", "### Current State", and "### For Next Session")
unchanged.
- Around line 1-17: The file lacks a top-level heading after the YAML
frontmatter (MD041); open .claude/commands/kb-handoff.md and add an H1
immediately after the closing frontmatter marker (the trailing '---') — e.g., a
concise heading like "KB Handoff" or "End-of-session Handoff" — so the document
contains a top-level heading directly following the frontmatter to satisfy
markdownlint.

Comment on lines +1 to +17
---
allowed-tools:
- mcp__gitkb__kb_context
- mcp__gitkb__kb_show
- mcp__gitkb__kb_list
- mcp__gitkb__kb_checkout
- mcp__gitkb__kb_status
- mcp__gitkb__kb_diff
- mcp__gitkb__kb_commit
- mcp__gitkb__kb_set
- Bash(git kb:*)
- Read
- Edit
description: End-of-session handoff — update context, log progress, commit pending changes
---

Prepare for session end or agent handoff. Ensures all work-in-progress is captured and context documents are fresh for the next session.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Add a top-level heading after frontmatter (MD041).

Markdownlint flags the lack of an H1. If frontmatter is required, add a heading immediately after it (or explicitly configure MD041 to ignore frontmatter-only files).

📝 Suggested fix
 ---
 allowed-tools:
   - mcp__gitkb__kb_context
@@
 description: End-of-session handoff — update context, log progress, commit pending changes
 ---
 
+ # KB Handoff
+
 Prepare for session end or agent handoff. Ensures all work-in-progress is captured and context documents are fresh for the next session.
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 17-17: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.claude/commands/kb-handoff.md around lines 1 - 17, The file lacks a
top-level heading after the YAML frontmatter (MD041); open
.claude/commands/kb-handoff.md and add an H1 immediately after the closing
frontmatter marker (the trailing '---') — e.g., a concise heading like "KB
Handoff" or "End-of-session Handoff" — so the document contains a top-level
heading directly following the frontmatter to satisfy markdownlint.

Comment on lines +74 to +89
```
## Session Handoff

### What Was Done
- [Summary of work completed]

### Current State
- Active tasks: [list with status]
- Pending work: [what's next]
- Blockers: [if any]

### For Next Session
- Start with: /kb-context to load project state
- Then: /kb-start <suggested-task> to resume work
- Watch out for: [any gotchas or context the next session needs]
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Specify a language for the fenced block (MD040).

The code block lacks a language specifier.

📝 Suggested fix
-```
+```text
 ## Session Handoff
 
 ### What Was Done
@@
 - Start with: /kb-context to load project state
 - Then: /kb-start <suggested-task> to resume work
 - Watch out for: [any gotchas or context the next session needs]
</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion

🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 74-74: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.claude/commands/kb-handoff.md around lines 74 - 89, Add a language
specifier to the fenced code block starting with the triple backticks that
contains "## Session Handoff" (e.g., change the opening ``` to ```text or ```md)
so the code block passes MD040; update the opening fence only and leave the
block contents (the headings and list items such as "### What Was Done", "###
Current State", and "### For Next Session") unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant