Generates detailed EXPLAINED.md documentation for User Stories from git diffs.
npx skills add https://github.com/ricardoo022/4dill --skill document-us-ricardoo022
Please help me install this Agent Skill. Skill: document-us Source: https://github.com/ricardoo022/4dill/tree/main/.gemini/skills/document-us Command: npx skills add https://github.com/ricardoo022/4dill --skill document-us-ricardoo022
High-intent search queries and answers about installing and using this skill.
Run the skill on a feature branch named feature/US-XXX-description. It reads git diff main...HEAD, the commit log, and docs/USER-STORIES.md, then writes a structured EXPLAINED.md covering every changed file under docs/Epics/<Epic Folder>/.
The doc follows the pattern in references/doc-pattern.md: Obsidian frontmatter tags, a Contexto section, per-file sections with actual code blocks and explanation tables, optional PentAGI Go references, and a mandatory Related Notes section using Obsidian wikilinks.
Yes. The generated docs are designed for Obsidian: they use [[wikilinks]] in the Related Notes section for graph navigation, valid frontmatter tags, and explicit Markdown links only when note names are ambiguous.
Prose and section headings are written in Portuguese, while code, variable names, and comments inside code blocks remain in English, matching the project's established Epics documentation convention.
The skill only explains code added or modified in the current branch's diff, so pre-existing code is covered only when essential for context. It also depends on the branch naming convention feature/US-XXX and the presence of docs/USER-STORIES.md to resolve the epic.
I-SynergyDraft user stories with Gherkin acceptance criteria for bounded contexts.
taracodlabsManages the full GitHub pull request lifecycle using the gh CLI.
canonicalCross-reference documentation claims, CLI commands, and API signatures against source code.
HomericIntelligenceGenerates API reference documentation from Python docstrings using pdoc or Sphinx.
