flowing-abyss
Community@flowing-abyss
flowing-abyss provides 43 skills for Obsidian vault management, structured note-taking, and disciplined software development practices like TDD and code review.
Agent Skills by flowing-abyss
Showing 43 vetted skills indexed across 2 GitHub repositories.
flowing-abyssusing-git-worktrees
Creates isolated git worktree workspaces with native tool detection and baseline test verification.
flowing-abysstest-driven-development
Enforces test-first development using the red-green-refactor cycle for features and bugfixes.
flowing-abysssystematic-debugging
Diagnose bugs through a four-phase root cause investigation process before proposing fixes.
flowing-abyssreleasing-an-obsidian-plugin
Automates versioned releases of an Obsidian plugin with verification, tagging, and GitHub release confirmation.
flowing-abyssusing-superpowers
Enforces skill discovery and invocation before any agent response or action.
flowing-abyssdispatching-parallel-agents
Dispatch concurrent subagents to fix independent test failures across separate problem domains.
flowing-abysscontext-engineering
Configures rules files and curates context layers for AI coding agents.
flowing-abyssexecuting-plans
Executes written implementation plans with review checkpoints and verification steps.
flowing-abyssfinishing-a-development-branch
Guides merging, pushing, or preserving a completed development branch with test verification and worktree cleanup.
flowing-abyssrisk-based-verification
Designs and executes a risk-based verification matrix for behavior-changing code work.
flowing-abyssbrainstorming
Guides collaborative design exploration and produces approved spec documents before implementation.
flowing-abyssdeprecation-and-migration
Plan and execute deprecation of legacy systems with incremental migration patterns.
flowing-abysswriting-plans
Generates detailed multi-task implementation plans with TDD steps from a specification.
flowing-abyssobservability-and-instrumentation
Implements user-visible error notices and debuggable console logging for Obsidian plugin failures.
flowing-abyssrequesting-code-review
Dispatches a code reviewer subagent to evaluate git diffs against requirements.
flowing-abyssreceiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
flowing-abysswriting-skills
Create and test agent skills using test-driven development with pressure scenarios.
flowing-abysssource-driven-development
Grounds framework-specific code decisions in fetched official documentation with cited sources.
flowing-abyssverification-before-completion
Enforces running verification commands before claiming work is complete or passing.
flowing-abysssubagent-driven-development
Executes implementation plans by dispatching fresh subagents per task with per-task and final code reviews.
flowing-abyssmonthly-review
Compute monthly velocity, themes, stale notes, and project health into a structured callout.
flowing-abyssyearly-review
Aggregates quarterly and daily notes into a structured yearly review.
flowing-abyssobsidian-flashcards
Generate Anki-ready flashcards from Obsidian notes with YAML frontmatter.
flowing-abyssobsidian-bases
Create and edit YAML-based .base files with filters, views, and formulas.
Frequently Asked Questions About flowing-abyss
FAQPage SchemaWhat tasks can I accomplish with flowing-abyss's skills?▼
You can manage Obsidian vaults end-to-end: create notes with YAML frontmatter, generate periodic reviews, build flashcards, produce Mermaid and Excalidraw diagrams, and format GTD tasks. A second skill set covers development discipline: TDD, debugging, code review, git worktrees, and release management.
Who are these skills designed for?▼
Two audiences: knowledge workers running Obsidian-based personal knowledge management systems who need structured notes, reviews, and visualizations; and software engineers who want enforced rigor around planning, testing, debugging, code review, and verification before claiming work complete.
How do the development-process skills work in practice?▼
Skills like test-driven-development, systematic-debugging, and verification-before-completion trigger at specific lifecycle points: before writing implementation code, when encountering bugs, and before claiming completion. They require running verification commands and citing evidence rather than making unsupported success assertions.
What prerequisites do these skills require?▼
The Obsidian skills require an Obsidian vault and, for obsidian-cli, the Obsidian CLI installed. The releasing-an-obsidian-plugin skill requires an existing Obsidian plugin repository with GitHub access. Development skills assume a git-based project with a test suite.
Can I create new skills using this registry?▼
Yes. The skill-creator and writing-skills entries cover authoring, editing, packaging, and verifying new skills from standardized SKILL.md frontmatter, including validating that skills function correctly before deployment.