# How to View Recent Wiki Commits in ai‑memory using git log

> Easily view recent wiki commits in ai-memory with git log. Learn how to check markdown file changes in the docs directory. Fast and efficient Git commands.

- Repository: [Fabio Akita/ai-memory](https://github.com/akitaonrails/ai-memory)
- Tags: how-to-guide
- Published: 2026-08-31

---

**Run `git log -- docs/` from the repository root to view recent wiki commits, since ai‑memory stores all wiki pages as markdown files in the `docs/` directory.**

The akitaonrails/ai‑memory project maintains its documentation as a flat-file wiki stored directly in the repository. Because every edit creates a standard Git commit, you can **view recent wiki commits in ai‑memory using git log** commands with path filters targeting the `docs/` directory.

## Understanding the ai‑memory Wiki Structure

In the repository, wiki content lives as individual markdown files inside the `docs/` folder. Unlike external wiki systems that use databases, this approach treats documentation as source code. Each page—such as [`docs/wiki-migrations.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/wiki-migrations.md) or [`docs/usage.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/usage.md)—is versioned alongside the application code, enabling standard Git workflows for auditing changes.

## Basic Command to View Recent Wiki Commits

To see the most recent changes across all wiki pages, run `git log` with a pathspec limiting the query to the `docs/` directory. The double hyphen (`--`) separates revision options from path arguments, ensuring Git interprets `docs/` as a file path rather than a branch name.

```bash
git log -n 10 -- docs/

```

This command displays the last ten commits that touched any file within the documentation folder, regardless of whether other parts of the repository changed in the same commit.

## Practical git log Examples for Wiki History

### Compact One-Line View

For a scannable overview suitable for terminal inspection or changelog generation, combine `--oneline` with `--decorate` to see abbreviated hashes, tags, and branch pointers:

```bash
git log -n 10 --oneline --decorate -- docs/

```

### Detailed Diff View for Specific Pages

When investigating changes to a particular article, specify the full file path and include the `-p` flag to show the patch (diff) for each commit. This reveals exactly which lines changed in documents like [`docs/wiki-migrations.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/wiki-migrations.md).

```bash
git log -p -- docs/wiki-migrations.md

```

### Filtering by Author and Date

Use standard Git revision filters to narrow results to specific contributors or time windows. This is useful for generating weekly reports or tracking a teammate's documentation updates:

```bash
git log --author="Jane Doe" --since="2 weeks ago" -- docs/

```

### Exporting Wiki History

To create an offline audit trail or generate release notes, format the output explicitly and redirect it to a file. The following example extracts the hash, date, author, and subject for the last twenty wiki commits:

```bash
git log -n 20 --pretty=format:"%h %ad %an %s" --date=short -- docs/ > recent-wiki.log

```

## Key Files and Directories

When running these commands, Git traverses the following paths:

- **`docs/`** – Root folder containing all markdown wiki pages. This is the primary pathspec for viewing wiki history.
- **[`docs/wiki-migrations.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/wiki-migrations.md)** – Example content file showing migration guidelines; useful for testing path-specific logs.
- **[`docs/usage.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/usage.md)** – Frequently edited user documentation demonstrating how individual page histories appear in logs.
- **`.git/`** – Internal Git metadata storing the actual commit objects that `git log` queries.

## Summary

- **View recent wiki commits in ai‑memory using git log** by filtering the `docs/` directory with `-- docs/`.
- Use `-n` to limit output to a specific number of recent commits.
- Add `--oneline` for compact terminal viewing or `-p` to inspect actual content changes.
- Specify individual file paths (e.g., [`docs/usage.md`](https://github.com/akitaonrails/ai-memory/blob/main/docs/usage.md)) to audit single articles rather than the entire wiki.
- Leverage `--author` and `--since` options to filter by contributor or date range.

## Frequently Asked Questions

### Where does ai‑memory store its wiki pages?

The project stores all wiki content as markdown files in the `docs/` directory at the repository root. Because these are standard text files tracked by Git, they appear in standard commit history alongside code changes.

### How do I see what content actually changed in a wiki page?

Append the `-p` (or `--patch`) flag to your `git log` command when targeting a specific file. For example, `git log -p -- docs/wiki-migrations.md` shows the full diff for every revision of that page.

### Can I filter wiki commits by specific authors?

Yes. Use the `--author` option followed by a name or email pattern. For instance, `git log --author="Jane Doe" -- docs/` returns only commits touching documentation files where the author matches the search string.

### Why is the `--` separator necessary in these commands?

The double hyphen tells Git that all following arguments are **pathspecs** (file or directory paths) rather than branch names, tags, or other revision identifiers. This prevents ambiguity when a filename matches a branch name and ensures `docs/` is interpreted as the documentation directory.