Menu
SkillsMP has collected 14 skills from hpbrn/creed. Open a skill to review its source and details.
Showing 14 of 14 collected skills.
Recognize and create valuable repository agent skills from concrete repeated workflows. Use automatically after meaningful work when a reusable workflow could prevent future errors or repetition, and when the user asks to add, create, build, or encode a skill.
Recognize and maintain repository agent skills from concrete usage evidence. Use automatically after meaningful work when a skill proves incomplete, incorrect, noisy, unsafe, or stale, and when the user asks to edit, fix, refine, reorganize, or update a skill.
Keep Creed source-code comments essential, durable, and useful to maintainers. Apply whenever adding, rewriting, reviewing, or auditing comments in code, stylesheets, scripts, tests, or migrations.
Create a clean, focused Git commit for completed repository work. Use when the user asks to commit, make a commit, save the work as a commit, or invokes /commit or $commit.
Write, edit, and review Creed user-facing language in its calm, precise, editorial voice. Apply automatically whenever changing product copy, marketing copy, onboarding text, UI labels, buttons, errors, toasts, prompts, documentation, pricing language, or…
Diagnose bugs, regressions, failing checks, unexpected behavior, and performance problems from concrete evidence before changing code. Apply automatically whenever the user asks to debug, investigate, fix a bug, explain a failure, or determine why something…
Keep Creed's standalone user documentation accurate, minimal, and aligned with shipped behavior. Apply automatically when changing apps/docs, setup or doctor flows, deployment and hosting support, configuration or environment variables, agent connections, MCP…
Design, implement, review, and verify safe Supabase Postgres schema migrations for Creed. Apply automatically whenever changing tables, columns, indexes, constraints, functions, triggers, RLS policies, grants, storage policies, or persisted data shapes.
Open or update a GitHub pull request with a squash-ready title and a plain prose description. Use when the user asks to open, create, update, or write a pull request, or invokes /pr or $pr. Do not use for local commits, versioning, merging, tagging, or…
Carefully improve existing code structure while preserving behavior. Use whenever the user asks to refactor, restructure, simplify, extract, consolidate, split, or clean up existing code.
Prepare and execute a verified Creed release across Git, packages, migrations, changelog, deployment, and publishing surfaces. Use only when the user explicitly asks to release, ship, publish, deploy, tag, or prepare a release.
Review completed repository code changes for actionable defects, regressions, unsafe behavior, and incomplete verification. Apply automatically after meaningful code edits and before claiming the work is done, and when the user asks to review, inspect, audit,…
Add a public Creed roadmap issue to the configured Linear project. Load only when the user invokes /roadmap or $roadmap. If they invoke it with no idea, ask what to add and wait. If they invoke it with an idea, draft the public card and create it. Do not load…
Prepare an intentional Creed product release using Semantic Versioning. Use when the user asks to release or version Open, Cloud, CLI, or Bench, or when a commit has explicitly been designated as a product release. Do not use merely because a commit targets…