All authors

Claude Skills by jupes
github.com/jupes48 skills0 installs74 views
- Add RepoRegister a new sub-repo in the knowledge base.Votes: 0GitHub stars: 2
- Add Unit TestsAdd focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.Votes: 0GitHub stars: 2
- Authoring Agent SkillsMeta-skill for creating Agent Forge skills under .claude/skills/ with SKILL.md, optional references/ and scripts/, and Bun scaffolds. Use when the user wants to add or author a skill, scaffold a new skill folder, or align skill docs with harness conventions (JSON script output, Beads for tasks).Votes: 0GitHub stars: 2
- Beads Priority AssignmentChoose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.Votes: 0GitHub stars: 2
- CavemanUltra-compressed communication mode that preserves technical accuracy while dropping filler. Use when the user explicitly says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.Votes: 0GitHub stars: 2
- Design An InterfaceGenerate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".Votes: 0GitHub stars: 2
- Domain ModelStress-test a plan against existing domain language, code behavior, and durable decisions. Use when the user wants DDD/domain-model grilling, glossary refinement, terminology challenges, context documentation, ADR candidates, or plan validation against a repo's language.Votes: 0GitHub stars: 2
- Edit ArticleEdit and improve article drafts by confirming a heading-based section plan, dependency order, then rewriting section by section with short paragraphs. Use when the user wants to revise or improve an article draft.Votes: 0GitHub stars: 2
- Forge ImplementPhase 3 of the Forge pipeline. Execute the plan's Beads tasks with red-green-refactor TDD, committing per checkpoint and pausing at each natural stopping point so the user can run a live demo or test and see the work themselves. Use when starting /forge-implement or the implement step of /forgemaster.Votes: 0GitHub stars: 2
- Forge PlanPhase 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.Votes: 0GitHub stars: 2
- Forge ResearchPhase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.Votes: 0GitHub stars: 2
- Forge ShipPhase 4 of the Forge pipeline. Summarize the whole workload — what was built, which Beads issues closed, a before/after, and a step-by-step walkthrough the user can run to verify it themselves — then run quality gates, push, and open the PR. Use when starting /forge-ship or the ship step of /forgemaster.Votes: 0GitHub stars: 2
- Git Guardrails Claude CodeSet up Claude Code git safety guardrails that block dangerous git commands before execution. Use when the user asks to prevent git push, hard reset, git clean, destructive checkout/restore, or branch deletion from Claude Code hooks.Votes: 0GitHub stars: 2
- Github TriageTriage GitHub issues through gh and a label-based state machine. Use when the user intentionally wants GitHub issue triage, incoming bug or feature review, issue workflow labels, needs-info follow-up, or ready-for-agent briefs.Votes: 0GitHub stars: 2
- Grill MeRelentlessly stress-test a plan or design through a one-question-at-a-time interview that researches available context first and includes a recommended answer with every question. Use when the user asks to "grill me", wants a plan/design challenged, or needs decisions resolved before implementation.Votes: 0GitHub stars: 2
- Improve Codebase ArchitectureSurface architectural friction and propose deepening opportunities that improve testability and AI-navigability. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase easier for agents to navigate.Votes: 0GitHub stars: 2
- Initiative Status ReportGenerate structured weekly status reports covering initiatives, progress, blockers, risks, and KPIs.Votes: 0GitHub stars: 2
- Migrate To ShoehornMigrate test files from `as` assertions to @total-typescript/shoehorn helpers. Use when tests need partial fixtures, intentionally invalid data, or safer replacements for TypeScript assertions.Votes: 0GitHub stars: 2
- Obsidian VaultSearch, create, and manage notes in an explicit Obsidian vault with title-case filenames, wikilinks, index notes, backlinks, and safe vault-root confirmation.Votes: 0GitHub stars: 2
- QaRun a conversational QA session where the user reports bugs or issues, and file durable Beads issues using project domain language. Use when the user wants to report bugs, do QA, file issues conversationally, or mentions a QA session.Votes: 0GitHub stars: 2
- Request Refactor PlanCreate a Beads-first refactor plan through detailed interview, repo verification, alternatives, scope boundaries, testing decisions, and tiny working increments. Use when the user wants to plan a refactor, write a refactoring RFC, or turn a risky change into safe incremental work.Votes: 0GitHub stars: 2
- Review PlanFact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.Votes: 0GitHub stars: 2
- Scaffold ExercisesScaffold course exercise directories with numbered sections, exercise variants, required readmes, and repo-specific validation. Use when creating exercise stubs, adding a course section, or safely renaming exercises.Votes: 0GitHub stars: 2
- Setup Pre CommitSet up repository-local Husky pre-commit hooks with lint-staged, Prettier, and optional typecheck/test gates. Use when a user asks to add pre-commit hooks, configure lint-staged, enforce staged formatting, or add commit-time checks.Votes: 0GitHub stars: 2
- Syncing ReposMulti-repo git operations — init, reset, status, branch management, refresh (rebase), stacked rebase. JSON output for agent consumption.Votes: 0GitHub stars: 2
- TddRun red-green-refactor in vertical slices, emphasizing behavior-first tests and harness quality gates.Votes: 0GitHub stars: 2
- To IssuesBreak a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.Votes: 0GitHub stars: 2
- To PrdSynthesize current context into a PRD and file it as a Beads feature/epic issue.Votes: 0GitHub stars: 2
- Triage IssueInvestigate a reported problem, diagnose root cause, and file a Beads issue with a behavior-level TDD fix plan.Votes: 0GitHub stars: 2
- Ubiquitous LanguageExtract a DDD-style domain glossary from conversation context, choosing canonical terms and flagging ambiguity. Use when the user asks to define domain terms, build a glossary, clarify terminology, create a ubiquitous language, or mentions domain modeling or DDD.Votes: 0GitHub stars: 2
- Ui Originality CriteriaGrade and steer UI work using Anthropic-style design dimensions—coherence, originality, craft, and usability—for generators and evaluators.Votes: 0GitHub stars: 2
- Zoom OutProduce a higher-level architecture and context map for unfamiliar code. Use when you need to understand how a file, module, feature, or issue fits into the bigger picture, including relevant modules, callers, callees, dependencies, and next context.Votes: 0GitHub stars: 2
- Add BeadCapture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.Votes: 0GitHub stars: 2
- AskAnswer questions about the codebase from knowledge files. Use when the user runs /ask or asks a domain/knowledge question about the repos.Votes: 0GitHub stars: 2
- Council/council — Deliberative multi-provider review. Use when the user runs /council.Votes: 0GitHub stars: 2
- Forge RolesReference definitions for the Agent Forge orchestration roles (lead, worker, planner, evaluator). Use when coordinating multi-agent Forge work or when you need one role's responsibilities and constraints.Votes: 0GitHub stars: 2
- Forgemaster AutoRun the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.Votes: 0GitHub stars: 2
- Forgemaster MiniTrimmed Forge pipeline (scope → build → wrap) for small, clear-scope work. Use when the user runs /forgemaster-mini or has a small, well-scoped task.Votes: 0GitHub stars: 2
- ForgemasterRoute a task by complexity and run the gated Forge pipeline (research → plan → implement → ship). Use when the user runs /forgemaster or wants the full guided feature pipeline.Votes: 0GitHub stars: 2
- GoClassify a task and route it to the right workflow (fix / feature / epic). Use when the user runs /go or wants the adaptive workflow router.Votes: 0GitHub stars: 2
- PlanExplore the codebase and produce an implementation plan. Use when the user runs /plan or wants a plan before building.Votes: 0GitHub stars: 2
- Pr DescriptionCanonical PR description template for every PR shipped from this harness, with a validator that enforces the required sections. Use when opening or editing a PR (the /ship and /forge-ship steps), or when asked for the standard PR format or to check a PR body.Votes: 0GitHub stars: 2
- ReviewRisk-tiered code review (Blocker / High / Medium / Low). Use when the user runs /review or wants the current branch or diff reviewed.Votes: 0GitHub stars: 2
- ShipRun quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.Votes: 0GitHub stars: 2
- StatusReport git state, ready work, blocked items, and PR health. Use when the user runs /status or wants a workspace snapshot.Votes: 0GitHub stars: 2
- Sync KnowledgeAuto-generate knowledge YAML from the codebase. Use when the user runs /sync-knowledge or wants knowledge files refreshed.Votes: 0GitHub stars: 2
- TriageDeadline management and capacity planning across epics and PRs. Use when the user runs /triage or wants deadline/capacity triage.Votes: 0GitHub stars: 2
- Ui ScreenshotAuto-capture UI screenshots for PRs using Playwright MCP browser tools.Votes: 0GitHub stars: 2