Yogev Lidor
Community@forhas
Yogev Lidor (forhas) builds a Notion-backed ticket lifecycle plugin covering requirement intake, plan review, code review, merge, and epic knowledge capture.
Agent Skills by Yogev Lidor
Showing 16 vetted skills indexed across 1 GitHub repositories.
forhasticket-system
Implements ticket CRUD and epic-container operations over a Notion database via the Notion MCP.
forhastask-breakdown
Analyzes a drafted ticket and decides whether it becomes one ticket or a multi-task mission.
forhassession-closeout
Enumerates unresolved session work from git and GitHub sources before final reporting.
forhasreview-and-merge
Drives a GitHub pull request through automated review rounds to a merged state.
forhasepic-update
Records resolved tickets against Notion epics by filing follow-ups, refreshing task lists, and closing completed epics.
forhasepic-doc
Maintains a single markdown brief per epic tracking status, open threads, and next tickets.
forhasissue-log
Records deduplicated, redacted runtime deviations from notion-dev workflows into a persistent Markdown issue log.
forhaslocal-code-review
Reviews pull-request diffs with severity-graded findings and a machine-parseable verdict line.
forhasknowledge
Manages an OKF knowledge bundle with retrieve, capture, curate, and migrate operations.
forhasflow-triage
Recommends feature-dev or superpowers build flow for a ticket using a codebase scout, scorecard, and outcome ledger.
forhasticket-interviewer
Interviews users to close requirement gaps in draft tickets before writeback.
forhasplan-review
Reviews implementation plans against the actual codebase with an independent agent before execution.
forhasinput-source
Dispatches requirement ingestion to prompt, existing-ticket, or Notion page sources and returns structured ticket input.
forhasdevelop
Drives a feature from one-line description to squash-merged commit via worktree, review, and cleanup.
forhasreceiving-code-review
Evaluates code review feedback with technical verification before implementing suggested changes.
forhasfeedback-harvest
Triage notion-dev client issue logs and apply warranted fixes in one pull request.
Frequently Asked Questions About Yogev Lidor
FAQPage SchemaWhat tasks can I accomplish with forhas's notion-dev skills?▼
You can ingest requirements from prompts or Notion pages, interview draft tickets, break work into Epics and Phases, triage tickets into feature-dev or superpowers flows, review implementation plans, run review-and-merge loops on pull requests, and close out sessions with enforced loose-end tracking.
Who are these skills designed for?▼
They target developers and plugin authors running the notion-dev command suite who manage tickets in a Notion database and want structured review, merge, and epic-documentation discipline. The feedback-harvest skill specifically serves the plugin author processing client runtime issue logs.
How do the review and merge skills work in practice?▼
review-and-merge resolves existing PR comments, loops the configured Codex or Copilot reviewer, and falls back to a local fresh-agent review producing severity-graded findings and a machine-parseable VERDICT line. It then merges per the configured strategy and deletes the remote branch.
What prerequisites and dependencies do these skills require?▼
ticket-system needs a configured Notion ticket database via Notion MCP and a .claude/notion-dev.config.json file. The knowledge skill invokes iwe alongside scripts/knowledge.py. Several skills are backend-agnostic or repo-agnostic and perform structural analysis only.
How does the plugin handle runtime errors and client feedback?▼
issue-log records deduplicated, redacted entries for MCP errors, misconfigured properties, retries, and aborts in the repo's notion-dev issue log. feedback-harvest later reads each client's log, assigns one of five dispositions per signature, applies fixes in a single pull request, and resets the logs.