All authors

Claude Skills by AndreVianna
github.com/AndreVianna114 skills0 installs0 views
- Aid Update JobUpdate an existing scheduled or background job. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Aid Update KbApply one targeted, human-confirmed change to the Knowledge Base. Use this skill when you know what changed and which part of the KB should reflect it, and you want that edit and nothing more. It works in its own worktree: it analyses how your instruction lands across the KB, turns that into a minimal scope plan with an explicit list of what it will not change, and pauses for your confirmation before any edit. Only the confirmed scope is applied, it is reviewed against the four-mandate panel,...Votes: 0GitHub stars: 6
- Aid Update MessagingUpdate an existing message/event schema or its emission. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Aid Update MvpRevise roadmap.md's ## MVP section only -- the first shippable slice: its contents, the line reasoning, what was cut, and its Status field (including the transition to Shipped <version>). Use this skill when the MVP section already carries committed content and its scope has changed. May create the ## MVP section if roadmap.md exists without one. Reads and consumes an MVP seed when one is present in `.aid/design/`; never requires one. Asks every run which previously created outputs to update ...Votes: 0GitHub stars: 6
- Aid Update RoadmapRevise roadmap.md's direction entries outside the ## MVP section -- add, revise or supersede direction entries, and move an entry between horizon sections (## Now, ## Next, ## Later). Use this skill when the roadmap already exists and something has moved between horizons. Reads and consumes a roadmap seed when one is present in `.aid/design/`; never requires one. Asks every run which previously created outputs to update alongside it -- no stored list, no tracking metadata written. The ## MVP ...Votes: 0GitHub stars: 6
- Aid Update StackRevise the project's technology (C0) Knowledge Base document -- languages, runtimes, frameworks, package managers, and build and test tooling with their versions, dependencies and constraints -- plus any previously created outputs you name. Use this skill when the technology-stack document already exists and a choice in it has changed. Requires no design seed: the change you state in the run is a sufficient input. Reads and consumes a stack seed when one is present in `.aid/design/`. When the...Votes: 0GitHub stars: 6
- Aid Update TestUpdate or extend existing tests. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Aid Update Testing StrategyRevise the project's quality (C6) documents -- the test landscape (levels, coverage expectations, CI lane mapping, known gaps) and the gate policy (what blocks a merge, the thresholds, who may waive one) -- plus any previously created outputs you name. Use this skill when the testing-strategy record already exists and a lane or a gate has changed. Requires no design seed: the change you state in the run is a sufficient input. Reads and consumes a testing-strategy seed when one is present in `...Votes: 0GitHub stars: 6
- Aid Update ThemeUpdate an existing visual theme or style-token set. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Aid Update TicketChange exactly one part of an existing ticket in the project's issue tracker. Use this skill when a ticket needs its description replaced, a comment added, or its status moved: `part` is the closed enum `description | comment | status`, and one invocation touches one of them. It resolves which tracker owns the ticket, loads whatever the named part needs, composes the exact mutation, and shows it to you for confirmation before the single write. A status target is checked against the tracker's ...Votes: 0GitHub stars: 6
- Aid Update UiUpdate an existing UI component or page. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Aid UpdateUpdate an existing internal code artifact's behavior under new acceptance criteria. Use this skill when you already know what to update and want it scoped, specified, and broken into reviewable tasks in a single pass, with no requirements interview. You approve the resulting plan before anything is built: this skill plans and stops, so run `/aid-execute` to carry the plan out.Votes: 0GitHub stars: 6
- Generate ProfileRegenerates the agents-only profile trees (profiles/<tool>/: agents + aid-tool.conf) from canonical/, then resyncs this repo's dogfood install. Maintainer-only tooling; never shipped to end users. State machine: LOAD -> VALIDATE -> RENDER -> VERIFY -> REPORT.Votes: 0GitHub stars: 6
- Release AidCut a release of THIS repo (the AID methodology repo) end-to-end: bump the version, update the release notes, gate, tag, publish to every channel, and verify all checks green. One level argument decides the bump: major | minor | patch | beta. Maintainer-only ops tooling — NOT an AID methodology skill, never rendered to profiles/, never shipped to adopters. Sequence: RESOLVE -> PRECHECK -> BUMP -> DOCS+NOTES -> PR(merge=human) -> DRY-RUN -> TAG -> VERIFY -> CONFIRM -> close-out.Votes: 0GitHub stars: 6