All authors

Claude Skills by eai-org
github.com/eai-org29 skills0 installs51 views
- Agentify ProjectMake a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit.Votes: 0GitHub stars: 55
- Check Ticket ImplementationCheck how much of a ticket is already implemented — split it into requirement blocks, judge each against the code, and save a human-readable TICKET-STATUS report in the planning dir.Votes: 0GitHub stars: 55
- Compact Docs WriterDraft, rewrite, or refine a doc for maximum token economy without losing any rule or intent. Use for docs kept in version control and regularly re-read by agents; skip throwaway docs like plans.Votes: 0GitHub stars: 55
- Compact Skill CreatorAuthor or refine a skill for maximum token economy without losing intent. Use when creating any new skill or editing an existing `SKILL.md`.Votes: 0GitHub stars: 55
- Context CheckupAudit what auto-loads into an agent session's context window and suggest lean, reversible fixes to cut startup tokens.Votes: 0GitHub stars: 55
- Create Implementation PlanTurn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.Votes: 0GitHub stars: 55
- Create Manual Test InstructionsTurn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.Votes: 0GitHub stars: 55
- Fetch Pr ReviewFetch all reviewer comments from a pull request URL (GitHub, Azure DevOps, …) and save them as a self-contained markdown PR-REVIEW file in the task's planning directory. Fetch only — no fixing or replying.Votes: 0GitHub stars: 55
- Fetch TicketFetch one or more tickets/issues from their tracker (Azure DevOps, Jira, GitHub, …) and save each as a self-contained markdown ticket file. Fetch only — no analysis or planning.Votes: 0GitHub stars: 55
- Fresh Eyes ReviewFresh-eyes review of a changeset by a fresh-context agent — catches regressions and correctness issues the authoring context reads past.Votes: 0GitHub stars: 55
- HandoverUse when handing finished work over to code review — writing a PR description or packaging a change for review by a human, an agent, or both.Votes: 0GitHub stars: 55
- Maintainer ReviewReview someone else's pull request as the maintainer deciding whether it merges — every prior comment walked, every claim verified, and nothing posted without your go-ahead.Votes: 0GitHub stars: 55
- Memory DoctorAudit the current project's agent-memory and, block by block, relocate each entry into a user-controlled home (project doc/skill/rule or user-level skill/rule) or archive it — draining memory so nothing uncontrolled accumulates in the agent's context.Votes: 0GitHub stars: 55
- Refine Pr ReviewTriage a fetched PR review with the user, comment by comment, drafting each reply and producing a REQUIREMENTS file for the accepted code changes. Takes the PR-REVIEW file produced by fetch-pr-review. Invoke manually only.Votes: 0GitHub stars: 55
- Refine TicketRefine a development ticket — or brainstorm a raw idea — into a validated, self-contained REQUIREMENTS document — the "what", verified against the codebase. Invoke manually only.Votes: 0GitHub stars: 55
- Review Code AssistantAssist a human reviewing a pull request or branch locally — diff a source branch against its target (auto-detected or from a PR link) and return concise, human-voice review comments with file and line locations. Read-only, never posts.Votes: 0GitHub stars: 55
- Review TicketTriage a ticket or ticket set before work starts — compare it against the codebase and save a review covering verdict, feature walkthrough, and only the high-cost questions worth raising.Votes: 0GitHub stars: 55
- Run Nx ChecksRun nx format, lint, test, and build on affected or specified projects, then fix unambiguous failuresVotes: 0GitHub stars: 55
- Self ImproveCapture durable user feedback into the governing skill/doc, or propose creating a new skill when no suitable one exists, so future sessions don't repeat the mistake. Use when the user rejects, reverts, or overrides the agent's output or approach on something a skill/doc covers or should cover, and when manually invoked to improve or create guidance.Votes: 0GitHub stars: 55
- Self ReviewSelf-review a changeset until merge-ready — a fresh-context reviewer checks it as a maintainer would, the author answers every finding, and a compact report for the PR proves the review happened.Votes: 0GitHub stars: 55
- Use Conversational LanguageVoice rules for text published under a person's name and read as if a person typed it, such as chat replies, PR comments and descriptions, commit messages, review replies, and code comments. Defines the wording only, never the content.Votes: 0GitHub stars: 55
- Verify UnderstandingVerify the engineer is ready to implement a feature — a teach-back conversation over a .TICKET-REVIEW.md where they explain the feature in their own words and the agent probes and corrects.Votes: 0GitHub stars: 55
- Execute Plan TasksExecute one task from a plan's task breakdown, verify it, tick it off, and hand back for review before the next one.Votes: 0GitHub stars: 55
- Split Plan TasksSplit a plan into small, individually reviewable tasks grouped into PR-sized batches, appended as a task section at the end of the plan file.Votes: 0GitHub stars: 55
- Attach To TicketAttach pasted images, files or URLs to a fetched ticket, saved beside its ticket file and referenced from it, or fill an attachment the fetch could not download. Local only — never queries or edits the tracker.Votes: 0GitHub stars: 55
- Explain In Simple LanguageExplain code, a decision, a recap, or a question to the user, or write a document a human reads to understand something, in simple language that a fluent but often non-native developer who did not see what the agent saw understands on the first read. Use when explaining or asking the user anything, when writing a review, report, or brief a human reads (never text sent under the user's name), or when the user asks for simpler words or says they did not understand. Changes the wording only, nev...Votes: 0GitHub stars: 55
- Prepare PromptPrepare a prompt that hands this session's work to a fresh agent session — to continue it, check it, or pick up what was left open. Use when asked for a prompt or brief for the next session.Votes: 0GitHub stars: 55
- Grill MeInterview the user relentlessly about a plan, design, or idea until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, validate an idea, get grilled on their design, or says "grill me".Votes: 0GitHub stars: 55
- Harden ArtifactHarden a REQUIREMENTS or PLAN document before the next phase picks it up — checked against its ticket, the code and related tickets, proven mistakes fixed in place.Votes: 0GitHub stars: 55