arfar-x

@arfar-x source repo

37 skills
0 followers
10 hours ago last updated

▌
Adr · arfar-x
Turns a design decision (with its context, options, and consequences) into a complete Architecture Decision Record (ADR) and saves it under docs/ADRs/ -- never makes the decision itself, only records one already made or being made. Use when the user asks to write/draft an ADR, record a design/architecture decision, or document why one option was chosen over another for future readers.

0 installs
▌
Prd · arfar-x
Turns a feature brief into a complete Product Requirement Document (PRD) and saves it under docs/PRDs/ -- never implements the request, only documents it. Also maintains CURRENT_STATE.md, a minimal navigation map of PRD implementation status. Use when the user asks to write/draft a PRD, spec out a feature, or turn a feature idea into a requirements doc for developers, QA, and stakeholders -- and when a feature/PRD is completed, started, a migration lands, a design decision is locked, or something is deferred and CURRENT_STATE.md needs updating.

0 installs
▌
Rfc · arfar-x
Turns a proposed technical/architecture change (with its problem statement, goals, proposed design, alternatives, risks, and rollout plan) into a complete Request for Comments (RFC) and saves it under docs/RFCs/ -- never implements the proposal itself, only documents it and opens it for review. Use when the user asks to write/draft an RFC, propose a system or architecture change, or open a design proposal for team review and discussion before work starts.

0 installs
▌
Trd · arfar-x
Turns a PRD, feature brief, or existing requirements into a complete Technical Requirements/Design Document (TRD) and saves it under docs/TRDs/ -- never implements the request, only documents the technical solution. Use when the user asks to write/draft a TRD, design the technical solution for a feature, or turn a PRD into an implementation-ready architecture doc for engineers, QA, DevOps, and security reviewers.

0 installs
▌
Jira · arfar-x bundle
High-level Jira assistant. Answers questions like "what should I work on next", "summarize my tickets", "what's blocking PAY-123", logs work, and moves tickets between statuses -- by calling structured Jira tools and reasoning over their JSON output, never by guessing or inventing ticket data. Use whenever the user asks about Jira issues, sprints, boards, worklogs, or ticket status.

0 installs
▌
Mood · arfar-x
Changes the tone/style the agent uses for the rest of the conversation -- neutral, alpha, angry, sarcastic, flatterer, or too-kind. Invoke as "/mood <mode>" or in plain language ("be angrier", "roast me", "be an alpha about this", "tone it down", "go back to normal"). Affects delivery only, never substance: never skips a safety refusal or a write-confirmation gate, never fabricates an answer, and is never directed at anyone outside this conversation.

0 installs
▌
Jira Log · arfar-x
Single entry point for worklog actions on a Jira issue -- logging new time, fixing an existing entry's duration/description/date, or deleting one. Routes to the right underlying action based on what's being asked. Use for "log 2h on PAY-123", "fix that worklog, wrong day", "delete that worklog I logged by mistake". Write operations, gated behind explicit user confirmation.

0 installs
▌
Telegram · arfar-x bundle
Reads, searches, and sends Telegram messages on the user's personal account via Telethon -- strictly scoped to chat_ids already present in TELEGRAM_ALLOWED_CHATS, with every single action (reads included) gated behind explicit confirmation. Use when the user asks to check, read, search, reply to, forward, or send Telegram messages, or to download Telegram media. Never for any other messaging platform, and never to authenticate, log in, or handle a phone number/code/2FA password.

0 installs
▌
Agents Md · arfar-x
Writes or updates an AGENTS.md file for a target project (or, for a monorepo, a root AGENTS.md plus nested per-subproject AGENTS.md files) -- the open, tool-agnostic convention (agents.md) that gives a coding agent the build/test/architecture/style context a README doesn't. Infers the project's real structure from workspace tooling and CI, not guesses. Searches the whole project tree for AGENTS.md files that already exist in subdirectories and inspects each for staleness or gaps -- without mechanically listing every one in the root's Project map, since agents already find the nearest one by directory proximity -- and asks the user before enhancing any of them. For a monorepo, asks before even scanning the tree for subdirectories that would benefit from their own nested AGENTS.md (that scan can be slow on a large repo), then asks again before creating any of the files it finds. A nested AGENTS.md this skill writes stays scoped to its own subtree -- it never restates the root file's overview or structure. Only

0 installs
▌
Task2code · arfar-x
Turns a Jira ticket into a reviewed pull request: reads the project's own AGENTS.md and existing git history for its conventions, fetches the ticket, plans the change, scaffolds and implements it, writes tests, runs the project's local quality gate, then commits and opens a PR -- pausing for explicit user confirmation at every irreversible step (branch creation, plan approval, commit, PR). Use when the user asks to implement a ticket, start work on a Jira issue, or turn a ticket into code.

0 installs
▌
Confluence · arfar-x bundle
High-level Confluence assistant. Answers questions like "what does the onboarding page say", "find the runbook for X", "summarize this page", and creates/updates pages, comments, and labels -- by calling structured Confluence tools and reasoning over their JSON output, never by guessing or inventing page content. Use whenever the user asks about Confluence pages, spaces, comments, or documentation.

0 installs
▌
Jira Board · arfar-x
What's happening on my board right now -- the active sprint if this is a Scrum project, or the column/status breakdown if it's Kanban. Auto-detects which one applies, so you don't need to know in advance. Use for "what's going on with my board", "what's the current sprint", "how's the board looking" when you're not sure which type of project this is.

0 installs
▌
Jira Track · arfar-x
Tracks what you're working on as the day goes, then turns it into Jira worklogs. Use when someone narrates their work rather than naming one ticket -- "I'm starting on X now", "two bugs came in, took me an hour", "after that I spent 3h on Y", "log my day", "what have I worked on today". Finds the matching issues, separates interruptions from focused work, and writes the time to Jira one confirmation at a time.

0 installs
▌
Jira Issues · arfar-x
Runs an arbitrary JQL search against Jira and returns structured issue results. Use for "find issues where...", "which of my tickets haven't been updated recently", or any query not covered by a more specific Jira skill.

0 installs
▌
Jira Sprint · arfar-x
Active sprint, board, dates, and goal. Use for "what's the current sprint", "when does this sprint end", "what's the sprint goal".

0 installs
▌
Jira Status · arfar-x
Moves a Jira issue to a new status. Use for "move PAY-123 to Review" or "close PAY-123". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Jira Triage · arfar-x
Groups unresolved Jira stories/bugs/tasks with their labeled subtasks to determine which ones need frontend work, backend work, or design/Figma readiness, and which ones haven't been broken into subtasks yet and need manual triage. Use for "which tasks have no subtasks yet", "which need frontend vs backend", "which stories still need triage".

0 installs
▌
Jira My Work · arfar-x
Lists unresolved Jira issues assigned to the current user, ordered by priority and recency. Use for "what should I work on next", "what are my open tickets", "summarize my tickets".

0 installs
▌
Jira Worklog · arfar-x
Logs time against a Jira issue. Use for "log 2h on PAY-123" or "I spent 30 minutes on PAY-123 today". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Jira Blockers · arfar-x
Blocking status and reasons for one Jira issue (status flags, unresolved "blocked by" links, flagged comments). Use for "what's blocking PAY-123" or "is PAY-123 blocked".

0 installs
▌
Jira Edit Issue · arfar-x
Updates fields (summary, description, labels, assignee, priority, components) on an existing Jira issue or subtask. Use for "rename PAY-123", "reassign PAY-123 to John", "add the Backend label to PAY-101". This is a write operation gated behind explicit user confirmation. For moving an issue between statuses, use jira-status instead.

0 installs
▌
Confluence Search · arfar-x
Runs an arbitrary CQL query against Confluence and returns structured page results. Use for "find pages about X", "search Confluence for Y", or any lookup not covered by a more specific Confluence skill. This is a read-only operation.

0 installs
▌
Jira Create Issue · arfar-x
Creates a new Jira issue -- a parent work item (Story/Bug/Task/Epic) or a subtask under one. Use for "create a bug for X", "add a frontend subtask under PAY-100". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Jira Search Users · arfar-x
Looks up Jira users by name/email fragment and returns their account_id. Use to resolve a person's name (e.g. "John") into the account_id JQL and create_issue/edit_issue need for assignee filters/fields -- never guess or invent an account_id.

0 installs
▌
Jira Worklog Edit · arfar-x
Updates an existing Jira worklog entry's duration, description, or date. Use for "fix that worklog", "I logged the wrong date, change it to Tuesday", "change the description on that time log". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Strategic Compact · arfar-x bundle
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Use when a session is approaching a context limit and a task phase is a natural place to compact.

0 installs
▌
Jira Issue Summary · arfar-x
Full context for one Jira issue: fields, comments, worklogs, changelog, and links, as one document. Use for "summarize PAY-123" or "what's the status of PAY-123".

0 installs
▌
Jira Kanban Status · arfar-x
Column breakdown and per-column issue counts for a kanban board. Use for "what's on the board", "how many tickets are in review", or any "current sprint" question that turns out to be about a kanban project (no sprints) instead.

0 installs
▌
Confluence Get Page · arfar-x
Fetches a single Confluence page's content and metadata by its content id. Use for "what does page X say", "show me page 12345678", or as the first step in summarizing/editing a page once you know its id. This is a read-only operation.

0 installs
▌
Jira Worklog Delete · arfar-x
Permanently deletes a Jira worklog entry. Use for "delete that worklog", "remove the time I logged on PAY-123 by mistake". This is a destructive write operation gated behind explicit user confirmation.

0 installs
▌
Jira Worklog Report · arfar-x
Aggregate the current user's logged Jira time over a date range, compared against each touched issue's original estimate. Use for "how many hours did I log this week", "how much more than estimated did I work", "what did I get stuck on recently".

0 installs
▌
Jira Project Context · arfar-x
Returns a reference snapshot of a Jira project: its issue types, workflow statuses, components, priorities, assignable users, and labels in use. Use for "what statuses does this project use", "who's on this project", "what labels exist" -- or before filtering JQL on a status/label/assignee you're not sure is real, to verify it instead of guessing.

0 installs
▌
Confluence Add Comment · arfar-x
Adds a comment to a Confluence page. Use for "leave a comment on page X saying Y" or "comment on this page". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Confluence Create Page · arfar-x
Creates a new Confluence page in a space, optionally as a child of an existing page. Use for "create a page in X called Y" or "add a new page under Z". This is a write operation gated behind explicit user confirmation.

0 installs
▌
Confluence Delete Page · arfar-x
Permanently deletes a Confluence page. Use for "delete page X" or "remove the old draft page". This is a destructive write operation gated behind explicit user confirmation.

0 installs
▌
Confluence List Spaces · arfar-x
Enumerates every Confluence space visible to the authenticated user. Use for "what spaces are there", "what's the key for the engineering space", or before creating a page when the destination space key isn't already known. This is a read-only operation.

0 installs
▌
Confluence Update Page · arfar-x
Updates an existing Confluence page's title and/or content. Use for "update page X to say Y", "add a section about Z to the runbook", or "rename this page". This is a write operation gated behind explicit user confirmation.

0 installs

37 published skills