sentimony
36 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
sentimonysession-learnings
You MUST use this when lasting learnings from the current session should be recorded for future agents - pitfalls hit, mistakes the user corrected, conventions found, or commands that finally worked, whatever the conversation language - including when the user asks to write down what the session taught and at the end of the awf chain after finalize. Records them without asking in the project's gitignored docs/session-learnings/AGENTS.md, linked from the root CLAUDE.md or AGENTS.md, each with its
- installs
- 19
- GitHub stars
- 4
- Updated
- Oct 26
sentimonyimplement
You MUST use this when an existing implementation plan is to be executed, either directly in the current session or through subagents, including resuming an interrupted execution from the plan's execution record, or when one or two edits with an obvious approach need doing without a plan. Covers task-by-task execution with evidence, drift handling and blockers, and a resumable execution record. Replaces devflow inline-plan-dev and subagent-plan-dev. Not for writing a plan (plan-craft), checking
- installs
- 15
- GitHub stars
- 4
- Updated
- Oct 26
sentimonyplan-craft
You MUST use this when a spec the user approved, an accepted design, or requirements already agreed in the conversation have to be turned into an ordered, multi-step implementation plan before any code is written - including a spec from specify, work with no spec yet, and a plan revision after a document review. Replaces devflow plan-crafting. Covers whether a plan is needed, task order, acceptance-criteria coverage, and the execution choice. Not for open design (specify) or executing a plan (im
- installs
- 15
- GitHub stars
- 4
- Updated
- Oct 26
sentimonycross-review
You MUST use this when an implementation plan or a finished implementation needs an independent review by other agent CLIs - by default the opposite CLI (Codex for work done in Claude Code, Claude Code for work done in Codex) together with Antigravity (Gemini) - whether the user asks for a cross-review or a second opinion from the other agent, or plan-crafting, inline-plan-dev, or subagent-plan-dev reach their cross-review step. Same-host implementation review belongs to review-request and decid
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonydashfix
You MUST use this when writing or substantively editing prose in a project (docs, READMEs, UI copy) and when asked to audit, count, score, or clean up dash usage - it enforces the plain hyphen over typographic dashes in text of any language.
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonydebugging
You MUST use this when investigating bugs, regressions, failing tests, build or integration failures, flaky behavior, performance anomalies, or other unexpected technical behavior.
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyfrontend-crafting
You MUST use this when building, implementing, redesigning, reviewing, or refining user-facing interfaces - including pages, layouts, forms, navigation, dashboards, and reusable UI components in HTML, CSS, Vue, Nuxt, React, or other frontend frameworks. Also applies to frontend code changes involving responsive design, styling, accessibility, visual hierarchy, interaction states, or user experience, even when the request is framed as implementation rather than design. Use alongside web-debug for
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonymaintaining-agent-context
You MUST use this when creating, auditing, optimizing, or maintaining repository agent instructions - AGENTS.md, CLAUDE.md, .claude/rules/, and instruction-related SKILL.md content - covering context architecture, always-loaded context cost, stale, duplicated, or conflicting instructions, and keeping agent memory aligned with the codebase. Not for human-facing documentation or skill authoring.
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonytdd
You MUST use this when implementing testable behavior changes - new features, bug fixes, or refactors with observable contracts. Covers writing meaningful failing tests before implementation and verifying behavior through the red-green-refactor cycle. Not for purely mechanical edits without behavior changes.
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonytypescript
You MUST use this when working on TypeScript-specific problems - compiler errors, tsconfig, strict typing, type inference, generics, complex type definitions, module resolution, ESM/CJS interoperability, type-checking performance, migration, or monorepo configuration. Also applies to designing or refactoring type-safe APIs, resolving framework type-checking issues, and improving type safety in existing code. Not for routine feature implementation where TypeScript types are incidental to the task
- installs
- 15
- GitHub stars
- 6
- Updated
- Oct 25
sentimonybranch-finish
You MUST use this when verified development work is ready for an integration or handoff decision - merging, pushing, opening a pull request, preserving or discarding a branch, or cleaning up its workspace. Covers safe completion choices based on the actual Git state and verification evidence.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyinline-plan-dev
You MUST use this when executing an existing implementation plan directly in the current agent session, including resuming interrupted execution. Covers task-by-task implementation, plan drift, and verification. Not for subagent-driven execution.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyparallel-agents
You MUST use this when several units of work might run concurrently through agents - independent investigations, specialist reviews, repository analyses, or plan tasks that look unrelated - covering whether they are genuinely independent, which mutable state needs isolation, how wide the wave should be, and how results are reconciled before integration.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyplan-crafting
You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyreview-request
You MUST use this when a completed or partially committed implementation needs an independent code review against explicit requirements, a defined task scope, and the actual Git diff, including committed and working-tree changes.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyreview-resolution
You MUST use this when code-review findings, PR comments, CI review output, or reviewer suggestions need technical validation before any fix or disposition, including feedback from human reviewers, subagents, GitHub, static-analysis tools, or external review systems.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyscope-triage
You MUST use this when a request needs design decisions before code - new features, product or UX behavior, architecture changes, unclear success criteria, or two materially different approaches. Explicitly specified mechanical refactors, localized fixes with known expected behavior, and single-outcome config changes go straight to implementation.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyskill-crafting
You MUST use this when deciding whether a recurring workflow needs a reusable agent skill, or when designing, creating, evaluating, improving, splitting, merging, or retiring skills. Covers trigger boundaries, architecture, behavior contracts, and effectiveness evaluation. Not for repository agent instruction maintenance (maintaining-agent-context), settled implementation planning (plan-crafting), or code behavior fixes (tdd).
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonysubagent-plan-dev
You MUST use this when executing an existing implementation plan through coordinated subagents, including resuming interrupted orchestration. Covers task delegation, review, verification, and integration. Not for inline plan execution or unrelated parallel investigations.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonyverification-gate
You MUST use this when work is about to be called complete, done, fixed, ready, or mergeable - before a completion claim, a merge or pull request, a branch finish, or a handoff report.
- installs
- 11
- GitHub stars
- 6
- Updated
- Oct 25
sentimonycr-received
You MUST use this when findings from a code review, pull request comments, CI or static-analysis output, or reviewer suggestions need a decision before any fix - a cr-request result, a spec or plan review, or a reviewer's message - in any programming language. Verifies each finding against the current tree, decides accept, reject, partial, defer, or escalate with evidence, fixes only what holds up, records the decisions in the plan's execution record, and routes back to verify. Replaces devflow
- installs
- 2
- GitHub stars
- 4
- Updated
- Oct 26
sentimonycr-request
You MUST use this when a change needs an independent review before it moves on - a finished task, a feature branch, a pull request, work-in-progress or uncommitted changes since a given ref, or a spec or plan document that needs review - in any programming language. Replaces devflow review-request. Pins the exact target and its tree fingerprint, gathers intent and constraints, and dispatches a read-only reviewer that returns separate verdicts and evidence-backed findings.
- installs
- 2
- GitHub stars
- 4
- Updated
- Oct 26
sentimonyfinalize
You MUST use this when verified work awaits a decision on how it leaves the branch - merging it, pushing it, opening a pull request (PR), keeping the branch, discarding the branch, or cleaning up a worktree or workspace - in any repository. Not for work that is not verified yet (verify), open review findings (cr-received), a plain commit with no integration decision, or release work with its own checklist. Replaces devflow branch-finish.
- installs
- 2
- GitHub stars
- 4
- Updated
- Oct 26
sentimonyspecify
You MUST use this when work has to be designed before any code is written - a new feature, a change to product or UX behavior, an architecture change, success criteria that are still unclear, or a choice between two materially different approaches - including a spec revision after a document review. A fully specified mechanical refactor, a localized fix whose expected behavior is known, or a config change with a single possible outcome gets no spec; the skill hands it to implement in one sentenc
- installs
- 2
- GitHub stars
- 4
- Updated
- Oct 26