research
claudeResearch memory between Obsidian and NotebookLM, with the obsidian-vault MCP server.
2 skills · 1 MCP server
Development workflow: bugfix and feedback skills, and worklog time-ledger hooks.
Plugin devflow from marketplace agent-station in ABilenduke/agent-station. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
bugfixInvestigate and fix reported defects or regressions through reproduction, causal diagnosis, and proportionate verification, keeping diagnosis-only requests read-only and leaving feature work or existing-plan execution to their own workflows.
feature-briefUse when the user wants to start, scope or kick off a feature, enhancement, spike or product idea and keep its record on a GitHub issue, asks for a feature or research brief, or hands over an issue that has not been briefed yet. Not for bug fixes (bugfix), answering a question that is already briefe
feature-executeUse when implementing or resuming an approved plan on a GitHub issue (its spec and plan sections), when the user says to carry on with an issue, or when asked to execute a feature while keeping its journal and timings. Not for ordinary coding without a plan, drafting or revising a plan, or reviewing
feature-planUse when a GitHub issue needs its spec, requirements, acceptance criteria, implementation plan, delivery steps or estimates, usually after its brief (and research) exist, when the user asks for a BRD, PRD or plan, or when an approved plan must change. Not for implementing the plan or reviewing deliv
feature-researchUse when a briefed GitHub issue is ready for research, when asked for a research spike, feasibility study, option analysis or business case, when a technical decision needs evidence from the codebase and authoritative sources before planning, or when earlier research turns out to be wrong. Not for w
feature-reviewUse when checking delivered work against its GitHub issue's spec and plan before calling it done, when asked to review a feature implementation for acceptance coverage and completion claims, or when closing out an issue with its time and retro. Not for critiquing a plan, PR review comments (feedback
feedbackHandles a pull request review cycle: reads the PR's review comments, applies each fix as its own commit, and records what changed on the PR itself, without adding files to the repository. Use when the user says "feedback", "PR feedback", "address review comments", "handle the review", or has review
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
d="${WORKLOG_STATE_DIR:-/tmp/worklog-$(id -u)}"; if [ -s "$d/active.json" ]; then node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" hook; else cat >/dev/null; fi; exit 0
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 skills
Claude Code skill for creating and presenting Slidev slidedecks
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.