Menu
SkillsMP has collected 17 skills from albertoirurueta/docs. Open a skill to review its source and details.
Showing 17 of 17 collected skills.
Set up an Antora documentation site in a repository that doesn't have one yet — installs Node.js/Antora prerequisites, scaffolds `docs/antora.yml` and `docs/antora-playbook.yml`, and builds a minimal ROOT module with `index.adoc`, `installation.adoc`, and…
Scan the repository for accidentally committed secrets (API keys, passwords, tokens, private keys, etc.) using the `detect-secrets` CLI (https://github.com/Yelp/detect-secrets). Checks whether `detect-secrets` is installed and, if it isn't, first checks for…
Analyze every Claude Code skill (`.claude/skills/*/SKILL.md`) and agent (custom definitions under `.claude/agents/*.md`, plus built-in agent types referenced from skills via the `Agent` tool) defined in this repository, and generate/update the Antora…
Execute the tasks in implementation_plan.md at the repository root, one at a time — implement each task per the plan, add or update tests achieving at least 80% coverage for the changed code, run the full test suite, verify the task introduced no new…
Draft and file a new GitHub issue that is ready to be picked up by the `/issue`, `/plan`, `/code` flow. Runs the `explore` skill first to ground the issue in the actual codebase, then asks the user for the purpose of the task to be implemented, then asks for…
Draft and file a new Jira ticket that is ready to be picked up by the `/issue`, `/plan`, `/code` flow. Runs the `explore` skill first to ground the ticket in the actual codebase, then asks the user for the purpose of the task to be implemented, then asks for…
Implement a single task from a .NET `implementation_plan.md`-style task list end-to-end — implementation, test-framework tests (xUnit/NUnit/MSTest, whichever the project uses), license headers, XML doc comments, a scoped test run, an 80% coverage check, a…
Run this .NET/C# project or solution's Roslyn analyzers — StyleCop.Analyzers for style/formatting (the .NET equivalent of Checkstyle) and Microsoft.CodeAnalysis.NetAnalyzers' CA rules for code-quality/design/reliability/security bug detection (the .NET…
Generate a code coverage report for a .NET project or solution via `dotnet test --collect:"XPlat Code Coverage"` (the Coverlet collector), scoped to the test selector given (same selector syntax as the `dotnet-test` skill), then read the generated…
Audit given C# class(es)/type(s) for complete XML doc-comment coverage — type-level `<summary>` (and `<typeparam>` for generics), every field/property/constant/event, every constructor/method (including private ones and any nested type or enum member) —…
Run a .NET project or solution's test suite via the .NET CLI (`dotnet test`), optionally scoped to specific test classes, methods, namespaces, or trait/category filters, and optionally targeted at a specific project (`.csproj`) or solution (`.sln`) file.…
Explore this repository codebase, optionally grounded in a specific GitHub issue or Jira ticket used as the task to investigate, and detect the programming language(s) and framework(s) in play — both in the existing codebase and in the requested change — plus…
End-to-end kickoff for a tracked ticket — a GitHub issue or a Jira ticket, auto-detected like `explore` — requires a ticket ID, unlike `explore`/`plan` this skill stops if none is given. Fetches the ticket, classifies it as a feature or a hotfix from its…
Implement a single task from a Java `implementation_plan.md`-style task list end-to-end — implementation, JUnit tests, license headers, Javadoc, a scoped test run, an 80% coverage check, a full-suite run, and a code-quality regression check against a…
Generate an implementation_plan.md at the repository root detailing the tasks needed to complete a piece of work, optionally grounded in a specific GitHub issue. Invoke as `/plan <issue-id>` to plan for that issue, or `/plan` with a description in the same…
Check the current branch's code changes and draft a brief, concise pull request description (emojis and diagrams allowed where they genuinely clarify). Detects which platform hosts the repository — GitHub, Bitbucket, Azure DevOps, or TFS — and uses that…
Review an already-open pull request's changes by id, on whichever platform hosts the repository (GitHub, Bitbucket, Azure DevOps, or TFS) and whatever language(s)/framework(s) are in play — both detected via the `explore` skill and used throughout instead of…