# Practice profile

Your Practice profile shows the feedback that Hephaestus gives you about patterns in your work, and how your work stands on each practice. It is private to you. Other developers see your observations only inside the counts on [Practices across the workspace](/next/user/practices-across-the-workspace.md).

![Practice profile with a standing ring of four practices and an open feedback card that names the practice and why it was raised.](/next/img/user/practice-profile/overview.light.webp)![Practice profile with a standing ring of four practices and an open feedback card that names the practice and why it was raised.](/next/img/user/practice-profile/overview.dark.webp)

To act on feedback:

1. Open a card under **Your recurring feedback patterns**.
2. Read **Why this was raised** and **Next step**.
3. Change your next piece of work, or [respond to the feedback](#respond-to-feedback).

## Open your Practice profile

1. Select a workspace.
2. Under **You**, select **Practice profile**.

A workspace that reviews practices opens on this page. A workspace that does not review practices has no Practice profile and opens on [Activity](/next/user/activity.md).

To learn the page, select **How to read this page** under the header. For a guided tour with examples, select **Take the tour**. Nothing in the tour changes your feedback.

## Where your feedback comes from

Hephaestus reviews your pull requests, merge requests, issues, conversations, documents, and the reviews that you write. Each review records observations against the practices of your workspace. Feedback about your reviewing stays on your own Practice profile or in your own conversation. The profile never compares you with other developers.

An AI model writes the observations, so a standing or a card can be wrong. [What Hephaestus can and cannot do](/next/user/ai-code-review.md#what-hephaestus-can-and-cannot-do) explains the limits.

Feedback that Hephaestus posts on a pull request, merge request, or issue stays on that work. It is not a card. [Find the feedback that a comment gave](#find-the-feedback-that-a-comment-gave) shows how to trace it.

Workspace admins can see all practice reviews, and instance admins can open a read-only view. [Your data in Hephaestus](/next/user/privacy.md#who-can-see-what) lists who sees what.

## Feedback cards

Each card describes one problem that recurs in your work on one practice. Each practice has at most one open card. A newer card for the same practice replaces the open card.

A card has four parts:

* The top names the practice and the work that the problem recurs in, such as *Recurring in three pull requests*. **Why this was raised** explains it.
* **Next step** says what to try.
* **Work reviewed for this practice** shows your recent reviewed work, oldest to newest. It counts how many more clean pieces of work resolve the card.
* The bottom gives the date, your rating, and **Disagree**.

To open the practice, select the card or **Learn more about this practice**.

The tabs list cards newest first:

* **Open** shows open cards. The page opens on this tab.
* **Resolved and closed** shows resolved and closed cards.
* **All** shows every card, including withdrawn cards.

### Card states

| State             | What it means                                                                                                                          |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Open**          | The card waits for clean work or for your response.                                                                                    |
| **Resolved**      | Three pieces of reviewed work in a row had no problem on the practice. Work that shows the problem again resets the count.             |
| **Marked by you** | You selected **I fixed this** or **Does not fit my work**. Your next reviewed work confirms it, and the count of clean work continues. |
| **Closed**        | Your workspace changed the review settings of the practice after the card was written.                                                 |
| **Withdrawn**     | A workspace admin withdrew the card because its words were wrong. It says nothing about your standing.                                 |

A resolved, marked, or closed card leaves the page 30 days after it changed state. A withdrawn card appears under **All** as a short notice without its text, only if the card reached you before. It accepts no response. [Corrections by workspace admins](/next/user/ai-code-review.md#corrections-by-workspace-admins) explains withdrawals and restores.

A card or an observation marked *Unverified history from an earlier review* does not show whether the current standard is met. You can read its text and evidence.

## Practice standing

The ring in the header counts your practices by standing:

* **Going well**
* **Mixed feedback**
* **Needs attention**
* **No standing yet**: no review in the last 90 days gave the practice a standing. The practice did not apply to your work, could not be judged, or was not reviewed.

A standing is read from your newest reviewed work on each practice. Your latest work counts most. If fewer than three pieces of work back a standing, its sentence calls it an early read. The next piece of work can change an early read.

A trend shows whether your recent work meets the practice more or less often than your work before it. It reads **Met more often**, **Met less often**, **No clear direction**, or **Not enough to compare**. To see how much work a standing or a trend rests on, point to its badge or select it.

A standing marked **Based on earlier reviews, the criteria might have changed** includes assessments from earlier reviews. They do not show whether the current criteria are met, and they give no trend.

A practice that your workspace stops reviewing leaves the page, with its standing and its feedback. The colors of the practice groups only tell the groups apart. They are not a rating.

## Read the evidence behind a standing

1. Select **See all practice groups**. The table lists each practice group with its standing, and what changed since the previous review.
2. Select a group.
3. Select a practice.

The practice has three tabs:

* **Feedback** shows your feedback cards for the practice. The practice opens on this tab.
* **Observations** shows the observations by review, newest first. Open one to read its explanation, problems, next steps, and evidence.
* **Guide** explains the practice and what work that meets it looks like, if the practice has a guide.

The timeframe beside the tabs narrows the feedback and the observations to the last 7, 30, or 90 days, or **All time**. Your open card always shows.

Practices and groups with no standing fold into one line at the end of their table. Select the line to see them.

To go back, select **Back**, or select a position in the path above the title.

### Find the feedback that a comment gave

1. Open the practice.
2. Select **Observations**.
3. Open the observation.
4. Under **Feedback from this observation**, select **Read the comment on the work**.

The box also says where else the observation gave feedback, such as on your practice page or in your conversation, and links to it.

### Compare with the workspace

The foot of **All practice groups**, of a group, and of a practice links to the same place on [Practices across the workspace](/next/user/practices-across-the-workspace.md). One **Back** returns you to where you started.

## Reviews of your work

The chip beside the title shows your latest review. It reads **Latest review** with the date and the work, or **Review running** while a review runs. Before your first review, it reads **No review yet**. While your first review waits or runs, the chip names the work, and it opens no list.

Select the chip to open **Reviews of your work**. It lists each review that recorded an observation about your work, newest first. A tag shows a review that someone asked for (**Requested**), that a schedule started (**Scheduled**), or that caught up on earlier work (**Backfilled**). **What it saw** counts the practices that the review recorded about you, by outcome.

* To open a review, select **See the reviewed practices**. Then select **Open observation** to read one observation in its practice.
* To see every review of one piece of work, select **Track this work** in its row.
* To narrow the list, use the **Work**, **Status**, and timeframe filters. **Reset** clears them.

## Respond to feedback

Answer feedback in Hephaestus. Replies and reactions on GitHub or GitLab do not save your answer. The footer of each Hephaestus comment says "Answer or disagree in Hephaestus" and links to your feedback on that work. Only the author of the work can answer there. Other people who follow the link see no feedback of their own.

### Mark feedback as fixed or not applicable

1. Open the card on your Practice profile, or follow the **Hephaestus** link in the comment footer.
2. Under **Or mark it yourself**, select **I fixed this** or **Does not fit my work**.

The card moves to **Marked by you**. After **Does not fit my work**, a later review of the same work does not send you that point again. To undo your answer, select it again. The card opens again.

### Disagree with feedback

1. On the card, select **Disagree**.
2. In **What is wrong in this feedback?**, enter one or two sentences.
3. Select **Send**.

Workspace admins read your sentence, not the card. They can mark the observation incorrect or withdraw the card. The card stays open until then. A disagreement does not change the observation or your standing by itself. While your disagreement stands, later reviews of the same work do not send you that point again. To take it back, select **Disagree** again.

### Rate feedback

1. At the bottom of the card, select **Helpful** or **Not helpful**.
2. Optional: Enter a note, and select **Send**.

A rating says whether the feedback helped you. It is separate from a disagreement, so removing your rating does not remove a disagreement. While a disagreement stands, its sentence is the only note on the card.

### Who sees your response

Workspace admins see that you have a current answer, when you gave it, and the sentence of a current disagreement. The card text, a rating without an answer, and your rating notes stay private. When you undo an answer, workspace admins stop seeing it, and its history stays.

## Request another review

Ask for another review after you change your work. You can ask as the author or an assignee of the work, or as a workspace admin.

1. Select the chip beside the title to open **Reviews of your work**.
2. In the row of the latest review of the work, select **Request another review**.
3. Optional: When Hephaestus accepts the request, select **View requested review** to follow it.

You can also ask in these places:

* **Request review** on your own open work in [Activity](/next/user/activity.md#request-a-review) or in the [Chrome extension](/next/user/browser-extension.md).
* A comment on a pull request or merge request that contains only `/hephaestus review`. An edited comment does not count. Comment from a GitHub or GitLab account that is connected to your Hephaestus account.

A request follows your [AI choice](/next/user/user-settings.md#your-ai-choice), the review scope of the workspace, and the access checks of GitHub or GitLab. If Hephaestus cannot accept the request, it says why, for example that a review was requested a short time ago. If nothing that the practices read changed since the last review, Hephaestus does not review the work again, and its observations stand. When a comment request ends without feedback, Hephaestus answers the comment and says why.

The new review keeps earlier observations in history. Of the reviews that can count, the one that Hephaestus recorded last counts, whoever started it.

## Before your first review

Before your first review, every practice reads **No standing yet**. The page lists what can start a review in your workspace, such as opening a pull request. Whether a review runs also depends on the repository and on each practice. **See what this workspace reviews** opens the practice groups. While your first review waits or runs, the page says so and links the work.

If no review can run on your work, the page names the reason. [No review ran on your work](/next/user/ai-code-review.md#no-review-ran-on-your-work) lists each reason and what to do.