agentleFS
encoreshaoencoreshao/encore-skills/AGENTS.md

encore-skills

AGENTS.md2 starsChanged 15 days agoMITView on GitHub

This project uses the encore-skills workflow library. AGENTS.md has no file-import syntax, so skill instructions are NOT duplicated here — skills/ stays the single source of truth. When a task matches a skill's description below, open its SKILL.md at the given path and follow it before proceeding.

The file

Files
AGENTS.md

Available Skills

This project uses the encore-skills workflow library. AGENTS.md has no file-import syntax, so skill instructions are NOT duplicated here — skills/ stays the single source of truth. When a task matches a skill's description below, open its SKILL.md at the given path and follow it before proceeding.

Skills

SkillPathWhen to use
analyze-issueskills/analyze-issue/SKILL.mdRead a GitLab issue, identify the root cause (not just symptoms), surface real risks, and produce an implementation approach before writing any code
create-mrskills/create-mr/SKILL.mdCreate a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved
eng-workflowskills/eng-workflow/SKILL.mdFull GitLab development loop — from issue to confirmed-resolved. Covers write-issue, analyze-issue, fix-issue, review-code, create-mr, summarize-issue, triage-issue, and post-merge verification.
fix-issueskills/fix-issue/SKILL.mdImplement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone
gitlab-configskills/gitlab-config/SKILL.mdWire up GitLab API access — multiple instances, project aliases, tokens. Run this once before any other GitLab skill.
pm-workflowskills/pm-workflow/SKILL.mdFull PM/designer loop — draft an issue, interact with users and stakeholders to validate it, refine until dev-ready, then finalize
review-codeskills/review-code/SKILL.mdPre-MR self-review — first confirm the problem is actually solved, then check for security, correctness, and simplicity
summarize-issueskills/summarize-issue/SKILL.mdAfter an issue is fixed and its MR is created, summarize the work in high-level markdown and post it as a comment on the GitLab issue
triage-issueskills/triage-issue/SKILL.mdUse when replying to comments on a GitLab issue, or when an issue has comments that might tag you or be waiting on your reply as assignee — figures out which comments genuinely need a response, drafts each reply grounded in the codebase, and posts after you confirm
write-issueskills/write-issue/SKILL.mdTurn a rough idea into a well-structured GitLab issue with clear problem statement, root cause, and testable acceptance criteria

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.